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

Annotations declare destructiveHint=true and readOnlyHint=false, and the description usefully disambiguates what that means here: 'nothing is sent, and the automation won't answer that message'. That is real added value beyond the annotations, since it tells the agent the destructive effect is limited to the draft itself. It doesn't say whether the rejection is reversible or whether the draft record persists.

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 the primary effect first ('turns down one waiting draft') and the consequence second. Every clause carries information; 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?

For a two-parameter state-change tool with no output schema, the description covers the key questions: which draft, where the ID comes from, and what actually happens downstream. The one meaningful gap is whether the draft is permanently discarded or can be restored, which matters given destructiveHint=true.

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% and both parameters already carry descriptions, so the schema does the heavy lifting. The description reinforces the provenance of draft_id but says nothing about the optional 'reason' field and adds no format or constraint detail beyond 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 names a specific verb ('turns down') and resource ('one waiting draft'), and the parenthetical anchors it to list_reply_drafts. An agent can tell it apart from approve_reply_draft and send_reply without opening any schema, though the contrast with approve_reply_draft is only implicit.

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?

It tells the agent the draft must be in the 'waiting' state and where to obtain draft_id (list_reply_drafts), which is clear operational context. It stops short of explicitly naming alternatives or stating when-not to use it (e.g., use send_reply or schedule_reply to actually respond).

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