ui_get_filters

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states the tool gets filters, but fails to mention that it is a read-only operation with no side effects, whether it requires any state to be initialized, or any other behavioral traits. For a getter, this is a significant gap.

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?

Single sentence with no wasted words. It front-loads the purpose and lists the filter types efficiently. Every word earns its place.

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?

Given the tool is a simple getter with no parameters and no output schema, the description covers the essential information: what it retrieves (active list filters) and which types are included. It lacks detail on the exact data structure or return format, but for a straightforward retrieval tool, this is mostly 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?

The tool has zero parameters, and the empty schema is fully covered. Baseline for zero parameters is 4. The description adds value by listing the filter types returned, which meaningfully describes the output even though it doesn't pertain to input parameters.

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?

Description clearly states it gets active list filters and enumerates the specific filter types: file_types, date_range, and folders. This distinguishes it from sibling tools like ui_set_filters (which sets filters) and other ui_get_* tools that retrieve different UI state components.

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 use when needing the current filters, but provides no explicit guidance on when to use versus alternatives (e.g., other UI getters) or any conditions for use. No when-not or alternative recommendations are given.

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