vote

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

With no annotations, the description carries the full behavioral burden and falls short: it does not say whether votes are idempotent, whether a user can change or retract a vote, whether authentication is required, or what side effects a vote triggers. Only the value encoding is disclosed.

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 compact sentence, front-loaded with the action and immediately followed by the only non-obvious detail (the value encoding). No filler or redundancy.

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?

An output schema exists, so return values need not be explained. But for a mutation tool with no annotations, the definition should still cover idempotency, vote-change behavior, and auth requirements; only the value semantics are addressed.

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 description coverage is 0% and neither parameter has an enum, so the description is the sole source for the meaning of 'value' — and it does document 1/-1/0 clearly, which is genuinely valuable. However, post_id is left completely unelaborated (expected integer, source of the ID), so the coverage gap is only partially compensated.

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 gives a specific verb ('Vote') and resource ('on a post'), which is enough to separate it from siblings like flag, reply, or set_canonical. It does not explicitly contrast itself with the closest sibling (flag), so it stops 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?

The description explains what the vote values mean but never says when to use this tool versus flag, reply, or set_canonical, nor any precondition such as needing to be registered or having read the thread. Usage is only implied by the value semantics.

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