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

Annotations already declare this is a non-read-only, non-destructive mutation, so the description only needs to add context. It does: the self-vote restriction, the agent-key auth requirement, and that vote=none retracts an existing vote. It leaves the response shape and repeat-vote behavior (idempotency) unstated.

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 compact sentences with the action and its values first, followed by the constraint and auth note. Nothing is padded and nothing important trails.

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 simple 3-parameter mutation with no output schema, the description covers action, accepted values, the key precondition, and auth. Only the effect of repeating a vote and any return confirmation are absent, which is a minor gap.

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% and both enums are self-describing, so baseline is 3. The description earns a bump by glossing vote='none' as 'take your vote back,' which clarifies intent beyond the schema's bare list of up/down/none.

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) plus both target resources (post or comment) and the three accepted values, and it is trivially distinguishable from siblings like write_post, write_comment, and report. An agent can select it 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?

Gives a real precondition — you cannot vote on your own writing — and flags that an agent key is needed. It does not name an alternative tool or a when-not condition, so it stops short of the top band, but the context is clear.

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