Show Recycled Incident

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, covering safety and idempotency. Description adds that it returns a JSON object and mentions required parameters and the API endpoint, which provides context but no new behavioral traits beyond annotations.

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?

Description is concise, front-loading the action and resource. Minor redundancy: 'specified Recycled Incident' and 'specific Incidents' are slightly repetitive. Overall efficient with no wasted sentences.

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 no output schema, description explains the return type ('a JSON object describing the requested Incidents'). It also includes the API endpoint for context. Pagination parameters exist in schema and are not described, which is acceptable for a single-resource fetch. Completeness is adequate for this simple tool.

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 has 100% coverage with descriptions for all parameters. Description restates required parameters (project_id, id) and shows their use in the endpoint path, but adds no new semantic meaning beyond what schema already provides.

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?

Description clearly states 'Returns the specified Recycled Incident' and 'fetch the full details of a specific Incidents by its identifier.' The verb 'fetch' and resource 'Recycled Incident' are specific, and the name distinguishes it from list_recycled_incidents and show_incident.

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?

Description says 'Use this to fetch the full details of a specific Incidents by its identifier,' implying it is for retrieving a single recycled incident. It does not explicitly contrast with alternatives like list_recycled_incidents or show_incident, but the purpose and naming make the use case clear.

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