List Checklist List Closed By Contact Filter Options

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds the return type ('JSON array of available filter values'), but does not add significant behavioral context beyond what annotations provide. No contradictions.

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 three sentences, front-loading purpose, usage, output, required param, and API location. It is efficient and avoids redundancy, though the API endpoint sentence is slightly extraneous for tool selection.

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 should specify the return structure more precisely. 'JSON array of available filter values' is vague; could mention typical fields (e.g., key, value). The required parameter is noted. Overall, it is adequate but not thorough.

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 each parameter (project_id, page, per_page) already described in the schema. The description simply restates 'Required parameters: project_id' without adding meaning like acceptable ranges or behavior details, so baseline score applies.

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 the tool lists closed-by-contact filter options for Inspections, with verbs like 'list', 'enumerate', and 'returns'. The name itself is descriptive. However, it does not explicitly distinguish from sibling filter options tools (e.g., inspector, location), though the name and context are sufficient.

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 provides usage context: 'Use this to enumerate Inspections when you need a paginated overview, to find IDs, or to filter by query parameters.' It gives concrete scenarios. However, it does not mention when not to use it or specify alternative tools for related tasks.

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