add_vote

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

There are no annotations, so the description must carry the behavioral disclosure burden. 'Add vote' reveals only the basic action and adds no information about permissions, reversibility, idempotency, side effects, or response behavior.

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 terse, but it is under-specified rather than helpfully concise. It restates the tool name and offers no structured information that would help an agent invoke or select the tool correctly.

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 mutation tool with no annotations and no output schema, this description is not complete enough. It omits the target resource, the expected effect beyond 'vote', and any relationship to related vote/watcher tools, so an agent cannot confidently understand the tool's full behavior.

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 100% and the parameter issueIdOrKey is already described as 'The ID or key of the issue.' The description adds no additional parameter semantics, which is acceptable given full schema coverage.

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 'Add vote' is essentially the tool name repeated, so it provides no independent clarification of what the tool does. It does not explicitly state that a vote is added to an issue, even though the only parameter is issueIdOrKey.

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?

No guidance is given about when to use add_vote versus the related siblings remove_vote or get_votes. The description does not mention whether the vote is for the current user, whether prior votes matter, or any condition that would favor this tool.

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