Show Incident Alert Recipient

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds the fact that the tool returns a JSON object and provides the endpoint path, but does not disclose additional behavioral traits beyond what annotations convey. 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 4 sentences, starting with the core purpose and then adding relevant details like required parameters and API endpoint. It is efficient but could be slightly more 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?

For a simple GET tool with no output schema, the description provides the endpoint path and return type (JSON object). However, it does not describe the structure of the returned object, pagination behavior, or potential errors. Given the simplicity, it is adequate but not complete.

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% description coverage for all 5 parameters. The description only repeats the names of required parameters without adding new meaning. It does not explain pagination parameters or their default values beyond what's in the schema.

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 that this tool returns a specific Incident Alert Recipient and fetches full details by identifier. However, there is a minor typo ('specific Incidents' instead of 'Incident Alert Recipient'), which causes slight ambiguity. The title and description align to distinguish it from sibling tools like show_incident or show_incident_action_type.

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 provide explicit guidance on when to use this tool versus alternatives, such as when to list all recipients vs. show one. It merely states 'Use this to fetch...' without context for appropriate usage. No when-not-to-use or alternative tools mentioned.

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