Show Item Response Set

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds context about the endpoint (Procore API, Project Management > Inspections) and return type ('Returns a JSON object'), but no additional behavioral traits beyond what annotations offer. 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 concise, consisting of a few clear sentences that start with the main purpose, then usage, return type, required params, and API context. Minimal redundancy.

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?

The description covers the main purpose and required parameters but has minor inconsistencies (e.g., uses 'Inspections' instead of 'Item Response Set'). No output schema exists, but the return type is mentioned. It does not address optional parameters like page/per_page, which could be irrelevant for a single-item endpoint.

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%, and the description only repeats that company_id and id are required. It does not add any new meaning or constraints beyond the schema's own parameter descriptions. Baseline score of 3 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: 'Returns a specified Checklist Item Response Set' and 'fetch the full details of a specific Inspections by its identifier.' The verb 'show' combined with the resource 'item response set' is specific, and the tool is easily distinguished from sibling tools like 'list_item_response_sets' and 'show_item_response_set_response'.

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 explains when to use this tool ('Use this to fetch the full details of a specific Inspections by its identifier') and lists required parameters. However, it does not explicitly state when not to use it or point to alternative tools, though the context implies differentiation from list and response-specific endpoints.

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