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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is largely covered. The description adds that a vote can be cleared (explaining the destructive hint) but says nothing about the required participant identity/token, per-participant scoping, or what state results after voting. With annotations carrying most of the burden, a 3 is appropriate.

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?

Two sentences, zero filler: the operation and its three modes come first, the invocation trigger second. Nothing is repeated from the schema or annotations.

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 five-required-parameter mutation with full annotation coverage and no output schema, the description covers what the tool does and when to call it. It could note that the participant token scopes the vote (so the agent knows whose vote changes), but no critical information is missing.

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 80%, so most parameters are documented structurally, and the enum for `vote` has no inline description. The description compensates by spelling out the three vote modes (up, down, clear), which is the key semantic the schema leaves implicit. It adds no detail on plan/participant parameters beyond what the schema already says.

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 names specific verbs (up-vote, down-vote, clear) and the exact resource (a participant's vote on a suggested place), which is clearly distinct from siblings like add_place or remove_entry. It does not explicitly contrast with any sibling, so it falls just short of a 5.

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?

"Use when the user expresses a preference for or against a place in the plan" gives a concrete trigger condition tied to user intent. There is no when-not guidance or named alternative (e.g., remove_entry for deleting a place), but the positive trigger is unambiguous.

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