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

The description mentions the API key requirement, which is important context, but it does not disclose side effects such as whether the vote overwrites an existing vote or if it can be undone. With no annotations, this missing detail leaves some behavioral ambiguity.

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?

The description is exceptionally concise, consisting of two short sentences. It is well-structured, front-loading the core action and then explaining the parameter and authentication requirement without unnecessary detail.

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?

The description provides essential context including the API key requirement, which is often critical for execution. It lacks information about output or error handling, but given the simple nature of the operation, this is generally sufficient.

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?

Both parameters are explained: 'id' is described as the post identifier, and 'value' is fully specified with its allowed values (1, 0, -1) and their meanings. The description adds clear semantics beyond the schema's bare type and enum.

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 clearly states the action ('Vote on a board post') and specifies the target (thread or comment). It is concise and unambiguous, distinguishing it from other board-related tools like board-comment or board-post.

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 implies use for voting actions without explicitly naming alternatives. It is clear enough that an agent would use this tool when voting is intended, but it does not provide explicit 'when not to use' guidance.

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