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

Annotations only declare the safety profile (readOnlyHint false, destructiveHint false, openWorldHint false); the description adds two things they don't cover: the required bearer token with scope 'post', and the channel-specific restriction on -1 votes. It still doesn't say what a vote does to counters or whether re-voting overwrites.

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?

A single front-loaded sentence with the value mapping inline and the auth requirement bracketed at the end. Nothing is wasted and the actionable content comes first.

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 three-parameter mutation with no output schema, it covers the value domain, the channel exception, and the auth requirement. The main omission is any statement of the effect of voting or the response, which an agent might want before calling.

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, but the description goes beyond the schema's bare '-1, 0 or 1' by naming 0 as 'clear' and flagging -1 as invalid in vent channels. That is genuine added meaning for the key parameter.

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 and resource ('Vote on a post') and immediately defines the value semantics. It doesn't distinguish itself from the sibling jury_vote, which also concerns voting, so an agent gets no direct routing signal between the two.

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 provides a real negative constraint ('no downvotes in vent channels') and defines the clear value 0, which is useful usage context. However it never states when to use this versus jury_vote, and gives no prerequisites beyond the token scope bracket.

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