List Checklist (Inspections) Items

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

Annotations already indicate read-only, idempotent, non-destructive. Description adds behavioral context: paginated, returns JSON array, includes pagination metadata, and references filtering capabilities. Does not contradict 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?

Description is a single paragraph covering purpose, usage, pagination, required params, and endpoint info. Includes a helpful link. Could be slightly more concise but is not verbose.

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?

No output schema, but description explains return type (paginated JSON array of Inspections) and mentions metadata. Adequate for a list endpoint. Does not compare to siblings but is complete for its own context.

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 parameters. Description adds value by naming required parameter and mentioning page/per_page for pagination, plus a link to filtering docs. But does not elaborate on filter parameters beyond schema.

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 lists checklist inspection items for a project, using specific verb 'Lists' and resource 'Checklist (Inspections) Items'. It differentiates from sibling tools like list_checklists_inspections by focusing on items rather than top-level inspections.

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?

Explicitly states when to use: for paginated overview, finding IDs, or filtering. Mentions filtering documentation link. However, does not provide guidance on when not to use or alternatives among siblings.

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