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

Annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=true; the description correctly frames the operation as a recorded decision rather than a publish. It clarifies the scope of the write (a review record, not consent) but does not explain what the destructive stamp means in practice — whether a review can be superseded or re-recorded, or how request_key replay behaves.

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 short, front-loaded sentences with no filler; the scope statement comes first and the disambiguation second. Nothing here is redundant.

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?

An output schema exists, so return values need no explanation, but this is a destructive, idempotent state change with five required parameters and zero schema documentation. Two sentences cannot cover revision mismatch behavior, idempotency, or the meaning of the three actions, leaving the definition under-specified for its complexity.

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% across six parameters, so the description carries the full burden. 'This exact saved draft revision' hints at expected_revision as a concurrency guard, but action values (approve/reject/needs_edit), reason, workspace_id, and the request_key idempotency contract are all left unaddressed.

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 ('Record') and resource ('editorial review of this exact saved draft revision'), which is enough for an agent to distinguish it from publish_social_draft and schedule_social_draft. It stops short of naming those siblings explicitly, so differentiation is implied rather than stated.

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 second sentence gives a useful exclusion ('not platform publishing consent or production approval'), which tells the agent this is not the tool for going live. However, it never says positively when to choose this over publish_social_draft, schedule_social_draft, or prepare_social_publication, nor what prerequisites a review requires.

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