As a platform, how should optional LTI features be handled to tool requests

Any thoughts from the community on this topic would be greatly appreciated.

When thinking about implementing an LTI platform, there are many optional tool features. For example, a tool may pass a "limit" parameter when using the membership service.

If a platform does not support a specific feature that the tool has requested, what are the recommended approaches to handle this?

Using the "limit" example above, if the platform doesn't support this feature, should it simply ignore the "limit" and return all results? Maybe it should return an error indicating the limit feature is not supported so the tool is aware of the limitation. This latter approach may cause some tools that work perfectly fine using platform X (that supports "limit") while receiving an error on another platform (does not support "limit").

Another example would be a tool providing the "rlid" parameter when interacting with the membership service. The tool clearly would like resource link request support. If the platform doesn't provide that then the tool surely needs to know.

Maybe, in the end, optional features should be handled on a case-by-case basis.

Thanks.