List Recycled Checklist (Inspection) Sections

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. Description adds behavioral context: pagination metadata, filtering capabilities, and endpoint URL. No contradictions. For a read-only tool, description complements annotations well.

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?

Four concise sentences with zero waste. Front-loaded with purpose, then usage, then parameter guidance, then API reference. Every sentence adds value.

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?

For a list tool with no output schema, description covers key aspects: paginated JSON array, pagination metadata, filtering by query parameters, required project_id. Could mention error handling or permissions beyond project_id, but sufficient for agent invocation.

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 has 100% description coverage for all 7 parameters. Description adds value by explaining pagination parameters ('Use page and per_page to control pagination') and states that response includes pagination metadata. This exceeds schema detail.

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 Recycled Checklist Sections from Checklists (Inspections) on the Project, distinguishing it from siblings that create/update/delete. It specifies use cases like paginated overview, finding IDs, and filtering.

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?

Gives explicit usage context: 'Use this to enumerate Inspections when you need a paginated overview, to find IDs, or to filter by query parameters.' However, it does not explicitly exclude scenarios or contrast with the non-recycled version, so slightly less guidance.

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