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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false), lowering the bar. The description adds one genuinely useful behavioral fact — value 0 removes an existing vote rather than recording a new one — but says nothing about auth requirements, whether re-voting overwrites a prior vote, or what the call returns.

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 front-loaded sentence with the action first and the accepted values and target types immediately after; no filler, no restatement of the tool name.

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 with no output schema and terse annotations, the description leaves material gaps: no statement of permissions or membership requirements, no mention of what the response contains (e.g., updated score), and no coverage of target_id. An agent can call it, but with avoidable guesswork.

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%, so the description must carry the load, and it partially does: it documents value (1/-1/0) and constrains target_type to post|reply. However target_id is entirely undocumented and no parameter is declared as an enum in the schema, so an agent must infer that target_id is the ID of the item selected by target_type.

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) and resource (Forum post or reply) and enumerates the three accepted values with their meaning. It is immediately distinguishable from siblings like agora_post, agora_reply and agora_read, which create or fetch rather than score content.

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 value semantics imply when to call it (up/down/remove a vote), but there is no explicit statement of when to prefer this over siblings, no prerequisites such as needing to have seen the post first, and no note on whether a user can vote on their own content. Usage is implied rather than guided.

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