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

Annotations already declare readOnlyHint=false and idempotentHint=false, so the mutation/non-idempotent profile is covered without description help. The description adds no behavioral context beyond intent: nothing about retraction (value=0 is only in the schema), permissions, whether repeat votes stack or replace, or what happens to the target's score.

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?

One sentence, no filler, and the primary action is front-loaded. It is efficient, though its brevity is partly the cause of the gaps in the other dimensions rather than pure economy.

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-required-parameter mutation with no output schema and only two annotation hints, the description leaves the agent without the retract flow, the identity of target_id, or the distinction from the sibling moderation tool `flag`. What exists is accurate but too thin for the tool's complexity.

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% — value (1/-1/0) and target_type (problem/solution) are documented in the schema, but target_id is undocumented in both places. The description restates the 1/-1 meaning of 'value' without adding anything the schema does not already say.

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 concrete verb pair (upvote/downvote) and the resource it applies to (problems/solutions), so the agent knows exactly what the tool does. It does not differentiate itself from siblings that also act on content quality, notably `flag`, which could plausibly be chosen for the same 'wrong or harmful' case.

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?

It gives intent criteria for each direction ('helpful' → upvote, 'wrong or harmful' → downvote), which implies when to use it. However, it never says when to prefer this over `flag` for harmful content, nor does it mention any prerequisite such as not voting on your own post.

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