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

Annotations flag destructiveHint=true and idempotentHint=true; the description adds substantive context: the draft 'stays in the approval queue' and 'this tool sends nothing', clarifying the side effect boundary. It does not explain what 'destructive' means here (e.g., does it overwrite unsaved edits?) or auth requirements, but it goes beyond raw 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?

Two dense sentences, front-loaded with the action and scope. Every clause earns its place by connecting sibling tools or clarifying side effects; no filler.

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?

Output schema exists, so return values need not be explained. The description is complete enough for correct invocation, though it could note whether rewriting requires the draft to be in a specific state or whether concurrent edits are overwritten.

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%, so baseline 3 applies. The description itself adds little parameter detail, though the schema's own descriptions (notably the three-name aliasing of 'text') already handle semantics thoroughly.

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?

States a specific verb+resource ('replaces the text of an outreach draft') with a precise scope qualifier ('that is waiting for approval'). This distinguishes it from send_outreach (sends) and list_pending_outreach (reads), making sibling differentiation explicit.

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?

Clearly situates the tool in the workflow: drafts come from list_pending_outreach, richer research from get_lead_memo. Implies when to use (editing a queued draft) but does not explicitly state exclusions or alternatives such as 'do not use for sent messages' — though 'sends nothing' covers the main boundary.

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