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

Annotations only declare it is a non-destructive, idempotent write; the description adds genuinely new behavior: vote weighting by job reputation, zero-weight votes from zero-reputation and internal operators, and a self-vote prohibition. It does not explain what happens when an operator re-votes (relevant given idempotentHint=true), keeping it short of a 5.

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 sentence that front-loads the core action and packs the constraints into a parenthetical, with no filler. The nested clauses are dense but every one carries rule information an agent needs.

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 write tool with no output schema, the description covers voting rules but omits the outcome of a re-vote (implied idempotent by annotations), error conditions for a rejected vote, and the effect on the lesson's score. It is adequate but leaves meaningful behavior 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 67%, with the direction enum and lesson_id format already documented in the schema. The description reinforces the up/down direction concept and ties lesson ownership to the lesson_id, but adds no syntax or format detail beyond what the schema provides, so the baseline 3 applies.

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 pair (upvote/downvote) on a specific resource (lesson), which immediately distinguishes it from the sibling vote_proposal and rate_skill. An agent can tell what the tool does without opening the schema.

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 gives eligibility constraints (one vote per operator, no self-votes) which imply when voting is valid, but it never names alternatives such as vote_proposal or explains when an agent should vote versus use another feedback mechanism. Usage is implied rather than routed.

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