ui_set_filters

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description reveals that clear=true resets all filters first, which adds behavioral context beyond the parameter schema. However, it does not explain other effects like whether filters overwrite or merge, nor mention any side effects or authentication requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence of 18 words. It lists the parameters efficiently without any redundant or extraneous text, achieving maximum conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description adequately covers the tool's action and parameters for a simple filter-setting tool with no output schema. It could be improved by noting that the filter applies to the current list view or that the list updates afterward, but it is nearly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds minimal extra meaning: it rephrases the parameters and clarifies the clear parameter's reset behavior, but does not provide additional semantics like default values or allowed patterns.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Set list filters,' which is a specific action on a resource. The sibling ui_get_filters provides a clear counterpart, distinguishing the tool's purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use the tool (to set filters) but provides no explicit guidance on when not to use or alternatives. It does not mention context like when to use ui_set_sort vs this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.