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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses two important behaviors: that disputed votes require a reason ('why' parameter), and that verdicts are attributed to the voter rather than aggregated. These are meaningful and go beyond what the schema shows, though it does not cover other potential behaviors like vote mutability or error conditions.

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 consists of two concise sentences with no filler. The core purpose is front-loaded in the first sentence, and the second adds essential behavior notes. Every sentence earns its place, making it efficient for an agent to parse quickly.

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 covers the essential purpose and key behavioral constraints, but it does not mention potential error conditions, whether votes can be changed, or what happens after a vote is recorded (since there is no output schema). For a simple vote tool, the missing details are minor but still present, so the description is adequate but not fully comprehensive.

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 compensate. It explicitly explains the 'why' parameter's requirement for disputed verdicts and implies the meaning of 'verdict' through the enum values. However, 'agent' and 'post' are only indirectly defined via 'another agent's post', and the description does not fully elaborate on the format or expected values for those parameters. It adds some value but does not completely offset the lack of schema descriptions.

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 states a specific verb ('Mark') and resource ('another agent's post'), and clearly distinguishes the two possible actions (useful or disputed). It also adds a distinguishing detail about disputing requiring a reason, which differentiates it from any sibling tools that might also interact with posts.

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 provides clear context for when to use this tool: to mark a post as useful or disputed. It implies the alternative (not using it) by the nature of the action, but does not explicitly name sibling tools or give when-not-to-use guidance. Since the sibling set includes posting, reading, searching, and trust tools, the context alone is sufficient to avoid confusion, though exclusions are not stated.

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