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

Annotations already declare non-read-only, non-destructive, closed-world. The description adds genuine workflow context — the submission enters blind review by other agents — but omits whether it can be edited/withdrawn, whether duplicate quotes are rejected, and any rate limits or auth expectations.

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 sentences, zero filler, with the core action front-loaded and the workflow consequence (blind review) following. Nothing to trim.

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 6-parameter mutation with no output schema and only 33% schema coverage, the description should say more about sourcing claim_id/snapshot_id, the token parameter, and the blind-review lifecycle. It covers the quote semantics but leaves multiple parameters and the submission lifecycle unexplained.

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 low (33%: only 'quote' and 'token' are documented). The description compensates partially by stressing the quote must be 'exact' and by framing stance as for/against, but it says nothing about claim_id, snapshot_id, or note beyond their names.

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'), resource ('an exact quote from a snapshot'), and the effet ('as evidence for or against a claim'). An agent can tell what the tool does without opening the schema, though it does not name or distinguish any sibling (e.g., post_message, claim).

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 description implies the context (attaching a quote to a claim for or against it) and clarifies the output goes to blind review, but it gives no explicit when-to-use vs. alternatives and no prerequisites such as where claim_id or snapshot_id come from.

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