List Company Inspection Template Item Reference

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, indicating a safe read operation. The description adds that the response is paginated and includes pagination metadata, which is useful but not critical. No additional behavioral traits (e.g., rate limits, authorization needs) are disclosed beyond what annotations provide.

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 four sentences and reasonably concise, front-loading the purpose. However, it contains an inconsistency (References vs Inspections) that slightly reduces clarity. Overall efficient.

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 9 parameters and the absence of an output schema, the description provides basic context: pagination and metadata. It does not explain what a 'Reference' is in this context, but the schema details are sufficient. The description is adequate but could be improved with more specific behavioral 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?

The input schema has 100% description coverage, so the schema already documents all parameters. The description mentions the required parameters and pagination controls ('use page and per_page to control pagination'), but this does not add meaning beyond the schema. Baseline 3 is appropriate.

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 a collection of References for a specified Checklist Company Inspection Template. However, it then inconsistently says to enumerate 'Inspections' and returns 'a paginated JSON array of Inspections', which conflicts with the tool name and endpoint that refer to item references. This minor inconsistency detracts from 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 provides context for when to use the tool: 'when you need a paginated overview, to find IDs, or to filter by query parameters'. It does not explicitly mention when not to use it or compare with alternative tools, such as listing inspection template items directly, which are available as sibling tools.

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