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

The description goes beyond annotations: it explains the toggle behavior (adding and removing), the deterministic anonymous ID mechanism, and that no API key is needed. These are behavioral details not captured in the annotations, which only mark destructiveHint. The description also clarifies identity consistency, which is valuable for the agent.

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 three sentences, each adding value: usage condition, toggle behavior, and identity mechanism. It is front-loaded with the most critical information (when to use) and avoids redundant details. No wasted words.

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 is quite complete for a simple tool with one parameter and an output schema. It covers identity, security (no API key), and the toggle nature. The only minor gap is that it doesn't state what the response contains, but the output schema presumably handles that. Given the simplicity and annotations, this is 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?

The schema already provides 100% coverage for the single parameter (post_id). The description does not add significant detail beyond the schema, but it does imply that the post_id must refer to a known post, which is a minor contextual addition. Baseline 3 is appropriate because the schema fully documents the parameter.

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 tool's purpose: to add or remove a vote on a specified VoteShip post, with a toggle behavior. It distinguishes itself from siblings by mentioning the specific resource type (VoteShip post) and the action (vote/unvote), which is not covered by siblings like submit_feature_request or browse_board.

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 explicitly states when to use this tool: 'when the user explicitly wants to add or remove their agent identity's vote on a known VoteShip post.' It also implies when not to use it by scoping to voting only, and mentions the alternative (submit_feature_request) indirectly by distinguishing vote from submission. The condition 'known post' gives clear usage context.

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