Show Injury

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds a deprecation note about response keys, which provides some context beyond the structured metadata, but does not disclose additional behaviors like pagination (despite page/per_page parameters being present).

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 cluttered with a deprecation note and contains a typo ('Incidents' for 'Injury'). It is not concise and could be streamlined.

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 is provided, yet the description only vaguely states 'Returns a JSON object describing the requested Incidents'. It fails to explain the response structure beyond deprecated keys, and does not address pagination parameters (page, per_page) or the incident_id parameter.

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 parameter descriptions. The description mentions required parameters (project_id, id) but adds no semantic detail beyond what the schema provides. The deprecation note references response keys, not parameters.

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 the tool 'Returns a specific Injury' and 'fetch the full details', but inconsistently refers to 'Incidents' instead of 'Injury'. It does not differentiate from sibling tools like show_incident, leaving scope ambiguous.

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?

No guidance on when to use this tool versus alternatives (e.g., list_injuries). No mention of prerequisites or when not to use.

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