get_recipient

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

With no annotations, the description must convey behavioral traits. It states 'Read-only' and shows the HTTP path, but fails to disclose required permissions, behavior on missing scanbox/recipient, or any side effects. The bare minimum is mentioned.

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 extremely brief (2 sentences plus a path), but this brevity comes at the cost of completeness. While there is no fluff, the minimal content does not adequately serve the agent. An average conciseness score is appropriate.

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 the tool has two required parameters and no output schema, the description lacks context about return values, error handling, or the resource model. The user gets no sense of what a 'recipient' is or what to expect from the response.

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 description does not explain the purpose of scanbox_id or recipient_id beyond their names. With 0% schema description coverage, the tool fails to add meaning to these parameters. Users are left guessing how to obtain valid IDs.

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 the tool retrieves a single recipient of a scanbox with 'Get one recipient of a scanbox. Read-only.' This specifies a verb (get) and resource (recipient), distinguishing it from sibling tools like list_recipients (list) and create_recipient (create).

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 is provided on when to use this tool versus alternatives such as list_recipients for multiple recipients or get_webhook_rule for other resources. The description omits any when-to-use or when-not-to-use context.

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