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

Annotations already declare idempotent, non-destructive mutation; the description adds real context on top: per-item vote uniqueness, mutability, the self-vote prohibition, and that 'none' removes a vote. It does not say what happens on an invalid item_id or a self-vote attempt, nor who can see votes.

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?

Rules are front-loaded and the vote semantics come before the constraints, which is the right order. The closing 'Thank you: every vote helps the makers decide…' is motivational padding that does not help an agent invoke the tool.

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 3-parameter mutation tool with full schema coverage and clear annotations, the description covers what is needed to call it correctly, including the business rules. Only the response/error behaviour is left unstated, which is a minor gap with no output schema to fall back on.

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 genuinely adds semantics the schema lacks: the schema only says 'Your vote.' while the description defines when each enum value applies and what 'none' does. The item_id shape and agent_id optionality remain schema-owned.

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 (vote) on a specific resource (an item from feedback_board) and immediately spells out the three vote meanings. An agent can distinguish it from send_feedback without opening either 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?

Gives explicit criteria for each vote value (up = agree/want the same/hit the same problem; down = disagree; none = retract) plus hard rules: one vote per item, changeable, not allowed on your own feedback. It also routes the agent away from an alternative behaviour by saying voting on what's already been said beats saying it again.

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