get_recipient

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

No annotations are provided, so the description carries the burden of conveying behavior. 'Retrieve' indicates a read-only operation with no destructive side effects, which is helpful. However, it does not disclose behavior around missing IDs, error responses, or what the returned recipient data includes.

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 a single, direct sentence with no wasted words. It conveys the essential operation and the identifying key immediately, making it easy for an agent to parse quickly.

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?

This is a simple single-parameter read operation with no output schema. The description accurately captures the tool's purpose and return expectation. It could be slightly richer by stating that it returns the full recipient object, but it is otherwise complete for the tool's low complexity.

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 fully documents the sole parameter, recipientId, with a description of 'The recipient ID'. The description adds only the 'by ID' qualifier, which is consistent with the schema but does not materially expand on it. Baseline 3 is appropriate given the high schema coverage.

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 uses a specific verb ('Retrieve') with a clear resource ('stored recipient') and the retrieval key ('by ID'). This distinguishes it from sibling tools like list_recipients, create_recipient, and update_recipient, which operate on collections or different actions.

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 phrase 'by ID' implies this tool should be used when a specific recipient ID is known, but it does not explicitly state when to use an alternative such as list_recipients. There is no direct mention of exclusions or routing among sibling tools, so the guidance remains implied rather than explicit.

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