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

Annotations declare a destructive, non-idempotent write; the description adds real context beyond them — that the outcome may be immediate publication or human-review queuing, that a distinct submit token is required, and a warning not to conflate publication with transaction verification. It stops short of covering irreversibility or duplicate-submission behavior that the destructive/non-idempotent hints imply.

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 required input, then the branching outcome, then the caveat. Each sentence carries distinct 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 single-parameter tool with no output schema, the description supplies the outcome variability, the status-reading instruction, and the semantic caveat, which is enough for correct invocation. Only the draft_id semantics and duplicate-submission risk are left unaddressed.

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?

Only one parameter (draft_id) with 0% schema description coverage, so the description must compensate. It references the 'consumer-confirmed draft' and a separate review:submit token, but never clarifies what draft_id refers to or where the token comes from — and the token isn't even a parameter here.

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 ('Submit') and resource ('consumer-confirmed draft'), which cleanly separates it from the sibling prepare_review that produces the draft. The jargon 'review:submit token' and 'self-reported review' are domain-specific but do identify the operation.

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 implies the prerequisite (a draft plus its separate review:submit token) and tells the agent to read the returned status, which is useful. However, it never explicitly states when to use this instead of prepare_review or reply_to_review, leaving routing to inference.

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