List Checklist List Inspector Filter Options

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint. Description adds behavioral details: pagination (page, per_page), optional search (query), and required parameters (company_id, project_id). No contradictions with annotations.

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 efficient, covering purpose, usage, parameters, and API reference in four sentences. It is front-loaded with the key action, but the first sentence could be more precise to avoid ambiguity between inspectors and inspections.

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 no output schema, the description explains the return type (JSON array of filter values) and includes the endpoint. It covers inputs, pagination, and search. Slightly more detail on the response structure would improve completeness.

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% with descriptions for all 7 parameters. The description highlights required parameters and the functionality of pagination and search, adding value beyond the schema by stating they are optional and when to use them.

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 it returns inspectors as filter options for inspections with pagination and search. However, the phrase 'enumerate Inspections' is slightly misleading as the tool returns inspector filter values, not inspections themselves. The title and description align on 'filter options'.

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?

Provides usage scenarios (paginated overview, find IDs, filter by query) but does not exclude alternatives or differentiate from similar sibling tools like the v1.0 variant. No explicit when-not-to-use guidance.

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