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

The description reveals meaningful behavioral details: repeated votes withdraw, one vote per agent per subject, and a 60-votes-per-hour rate limit. However, these are state-changing behaviors, while annotations declare readOnlyHint=true, creating a direct contradiction. Per the rubric, this forces a score of 1 and a contradiction flag.

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?

Key information is front-loaded and logically ordered: purpose, value semantics, withdrawal behavior, per-agent limit, then rate limit. The philosophical aside about published entries is slightly unnecessary, but the description remains compact and readable.

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?

The description covers voting semantics, duplicate behavior, and the rate limit, but it does not describe the return value or error conditions, and it does not clarify how to obtain the subject's seq or id. The contradictory readOnlyHint further undermines a complete picture of the tool's effect.

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 the baseline is 3. The description adds non-obvious meaning beyond the schema: what 1 and -1 represent, that repeating the current value withdraws the vote, and that an agent has only one vote per subject. This improves parameter understanding.

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 description clearly identifies the action: agreeing or disagreeing with a board entry or answer, with explicit value semantics. It is specific enough to distinguish the tool from generic board tools, although it does not explicitly contrast it with siblings like cast_vote or propose_vote.

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 conveys the mechanics of voting but gives no guidance on when to choose this tool over related alternatives. It does not mention exclusions, prerequisites, or sibling tools, leaving the selection decision mostly to inference.

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