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

Annotations already declare a non-destructive, non-open-world write, so the safety profile is covered. The description adds one genuine behavioral fact — the draft must be unsent — and 'Replace' implies whole-field overwrite rather than a merge, but it says nothing about failure modes for sent/missing threads or what the call returns.

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?

A single front-loaded sentence with no filler and the key constraint ('unsent') placed inline. It is efficient, though arguably too terse for a five-parameter mutation, which limits how much it can earn.

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 required-parameter-heavy mutation with 0% schema description coverage and no output schema, the description omits the identifier parameters, preconditions, and result behavior. What remains is a bare statement of intent, insufficient to call the tool confidently.

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 description coverage is 0% and all five parameters are required, yet the description only names two of them (subject, body). The three identifier parameters (projectId, siteId, threadId) are left entirely undocumented in both schema and prose, so the description fails to compensate for the coverage gap.

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 pairs a specific verb ('Replace') with the target fields ('subject and body') and the resource ('unsent draft'), so the action is unambiguous. It does not, however, name or contrast itself with close siblings like regenerate_outreach_draft or prepare_outreach_draft, which an agent must disambiguate on its own.

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 only usage signal is the implicit constraint that the draft must be 'unsent'; there is no explicit when-to-use statement and no mention of alternatives such as regenerate_outreach_draft or update_outreach_template. An agent gets no routing guidance.

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