Get A List Of Inspection Item Signature Requests

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

Annotations indicate readOnly, idempotent, and non-destructive behavior, which the description supports. However, the description incorrectly states that the tool returns 'a paginated JSON array of Inspections' instead of signature requests. This error undermines transparency and misinforms the agent.

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 has four sentences, but includes redundant and confusing phrasing ('Use this to fetch the full details of a specific Inspections'). The key information is present but not optimally front-loaded; the error reduces clarity.

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 tool's complexity (6 params, pagination, no output schema), the description should be more complete. It mentions pagination and required params but fails to accurately describe the return type. The incorrect statement about returning inspections is a significant omission that hinders proper use.

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 already covers all parameters with descriptions (100% coverage). The description adds minimal value by reiterating required parameters and pagination usage. It does not explain the 'filters__id' parameter beyond the schema, so it meets the baseline but adds little.

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 states 'Get a list of Inspection Item Signature Requests for a specified Inspection,' which clearly identifies the resource and action. However, it later says 'fetch the full details of a specific Inspections,' causing slight confusion. The name and context clarify the intent, but the mixed messaging prevents a top score.

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 does not specify when to use this tool over alternatives like 'list_checklist_signature_requests' or 'show_a_inspection_item_signature_request.' The misleading instruction 'Use this to fetch the full details of a specific Inspections' further detracts from usage guidance.

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