List Project Inspection Template Item Reference

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds useful behavioral details: paginated response with page/per_page, pagination metadata, required parameters, and the full API endpoint. It complements annotations without contradiction.

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 4 sentences, front-loaded with core purpose, followed by usage, return type, pagination details, required params, and API reference. It is efficient, though the term 'Inspections' could be corrected to 'References' for precision.

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, the description adequately conveys return format (paginated JSON array), pagination metadata, and required parameters. It also mentions filtering capability. While it could specify metadata fields, it is sufficiently complete given the high schema coverage and annotations.

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?

Input schema coverage is 100%, so baseline is 3. The description adds value by summarizing pagination control and required parameters, but does not elaborate on filter parameters (filters__id, etc.) beyond what the schema already provides. This is adequate but not exceptional.

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 Project Inspection Template, with a specific verb and resource. It distinguishes from siblings like 'list_company_inspection_template_item_reference' by mentioning the project context and endpoint path. However, it inconsistently refers to 'Inspections' instead of 'References', slightly reducing 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 gives explicit usage scenarios: 'to enumerate Inspections when you need a paginated overview, to find IDs, or to filter by query parameters.' It also lists required parameters. However, it does not mention when not to use this tool or explicitly differentiate from sibling tools for company-level references.

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