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

Annotations already declare readOnlyHint=false, idempotentHint=true, openWorldHint=true — so safety/idempotency are covered. The description adds real value beyond them: one vote per agent/version, changes are logged, and the caveat that votes are opinions and not authoritative. That's useful behavioral context, though it omits what version_conflict means and how weighted opinions behave.

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 with the exclusion rule front-loaded. Information-dense and no filler, though 'Votes are opinions' could be folded into the prior clause rather than standing as its own sentence.

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?

Covers the gating condition, idempotency, and evidence requirement, but for a 6-parameter tool with nested proof and no output schema, it leaves the version_conflict path (referenced only in the schema description) and any response behavior undocumented in the description itself.

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 100%, so every parameter including proof, sources, and reason is documented in the schema itself. The description adds no parameter-level detail beyond the schema; baseline 3 applies when the schema already does the heavy lifting.

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 first sentence implicitly establishes a negative vote on information, and the sibling upvote_information confirms the polarity. But the description never says outright that it casts a downvote on a record version — the verb+resource pair is inferred rather than stated, which is a step below the specific-verb standard.

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?

Gives a clear gate: 'Vote only if evidence you checked establishes a material error.' It also routes to read_information.review_policy and to prepare_credibility_vote (via the proof field). It does not name upvote_information as the contrasting alternative, so the when-nots remain implicit.

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