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

Annotations already declare readOnlyHint=false and destructiveHint=false, so safety profile is partly covered. The description adds real semantic context by mapping the actions to meanings (edit the draft vs. record a posted/dismissed outcome), but does not say what happens to the draft on dismissal, whether the change is reversible, or what the body requirement is.

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; the operation and its two resolution modes appear immediately, every clause earns its place.

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 5-parameter mutation tool with no output schema and 0% schema description coverage, the description is too thin — it never explains the required identifiers or what an agent must supply to edit vs. resolve. It should do more to compensate for the missing field documentation.

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 0% across 5 parameters, so the description carries the burden. It only loosely implies the 'body' for editing and the action values; the identifiers (projectId, siteId, mentionId) and maxLength constraints get no explanation in the description, leaving the schema to speak entirely for itself.

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 gives a specific verb+resource ('edit a drafted reply') and names the two status-recording modes ('posted' or 'dismissed'), aligning with the action enum. It distinguishes the write intent from read-oriented siblings like get_lead and from generate_lead_reply, though it does not explicitly contrast itself with those tools.

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?

Usage is implied by the phrase 'a drafted reply' and the three modes, but there is no explicit when-to-use vs. generate_lead_reply or review_outreach_reply, and no prerequisites stated. Adequate but with clear gaps.

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