Correct. They are not allowed in any assertion construct: sequence, property, or checker. This is something the IEEE committee considered, but has not gotten around to implementing in the standard.
But I think you can easily work around this as these constructs are all type-less; meaning you don’t have to specify any types for the arguments. And anything you might have wanted to declare as a parameter can be passed as an argument.
Very good point that arguments of those assertion constructs can be untyped. That probably solves my problem. Basically, the reason to ask that parameterization thing was originated by generate loop construct used inside the checker to create certain amount of generate blocks declared by the parameter. But, that type-less nature of arguments makes it possible.