Show Recycled Property Damage

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that it returns a JSON object and mentions the endpoint. No contradiction. For a read operation with annotations, the description provides adequate but not extensive additional context.

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, including purpose, usage, return type, required parameters, and API path in two sentences. No unnecessary words, front-loaded with key information.

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 says returns JSON object. For a show endpoint, this is mostly complete. However, optional parameters (incident_id, page, per_page) are in schema but not mentioned in description, which could be added for completeness, but schema covers them.

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 each parameter described. The description lists required parameters (project_id, id) but does not add new meaning beyond the schema. Baseline 3 is appropriate as the schema does the heavy lifting.

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 specified Recycled Property Damage record, uses specific verb 'Returns', identifies the resource (Recycled Property Damage record), and distinguishes from sibling tools like show_property_damage by specifying 'Recycled' and mentioning Incidents context.

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 says 'Use this to fetch the full details of a specific Incidents by its identifier.' It implies when to use it but does not explicitly state when not to or compare with alternatives like show_property_damage. The context is clear from the name, but a direct alternative mention would improve it.

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