List Checklist List Template Filter Options

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

Annotations indicate readOnlyHint=true and idempotentHint=true, which are clear. However, the description itself is contradictory (templates vs. filter values) and does not clarify behavioral traits beyond the annotations. It adds minimal value and introduces confusion.

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 paragraph of 4 sentences, adequately sized but includes redundant phrases and some misdirection. It could be more concise and accurate.

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 complexity of 7 parameters, no output schema, and many sibling filter option tools, the description fails to clarify the exact output ('JSON array of available filter values' is vague) and does not help the agent distinguish this tool from similar ones like 'list_checklist_list_template_filter_options_project_v1_0'.

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 input schema has 100% description coverage for all 7 parameters, so the baseline is 3. The description mentions required parameters and pagination/search, but does not add new meaning beyond what the schema already provides.

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 is inconsistent: it says 'Returns list templates associated to inspections' but also 'Returns a JSON array of available filter values for Inspections.' The tool name includes 'filter_options', so it likely returns filter option values, not the templates themselves. This ambiguity undermines purpose clarity.

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 states 'Use this to enumerate Inspections when you need a paginated overview, to find IDs, or to filter by query parameters,' but the tool is about list template filter options, not a direct inspection list. It does not differentiate from sibling tools like 'list_checklist_inspections' or other filter options tools, and provides no guidance on when not to use it.

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