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

Annotations already declare idempotent=true, destructive=false, readOnly=false, so the safety profile is partly covered. The description adds real behavioral detail beyond them: the saved body is overwritten with the suggestion, the record transitions to draft, and it stays unapproved until approve_sendable_wording. It omits auth requirements and what happens on a revision mismatch, but the state-transition disclosure is valuable.

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?

Three tight sentences, front-loaded with the action and its effect on the record, then the approval caveat, then the non-obvious parameter note. No wasted words.

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?

With an output schema present, return values need not be explained, and annotations cover the mutation safety profile. The description supplies the state transition and the parameter caveat, leaving only minor gaps like error handling on revision conflicts.

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%, so the description carries the burden. It usefully disambiguates expectedRevision ('the wording revision, not the suggestion'), a genuinely non-obvious distinction, but says nothing about suggestionId or the failure behavior when expectedRevision is stale.

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 (accept) and resource (an open suggestion) and describes the resulting state change. It also names the sibling that governs the follow-up approval, so an agent can distinguish it from approve_sendable_wording without opening either schema.

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 frames the context of use ('Accept an open suggestion') and routes the agent to approve_sendable_wording for the related approval step, showing it is distinct from approval. It does not mention dismiss_sendable_change as the competing alternative when a suggestion is rejected, so the when-not guidance is incomplete.

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