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

Annotations already declare non-readOnly, idempotent, non-destructive behavior, but the description adds meaningful context: vote replacement on direction switch, idempotency on repeat, and a required bearer token for Authorization. It goes beyond the annotations rather than merely restating them.

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 most important information (value semantics) is front-loaded, followed by vote-switching, idempotency, and auth. It is dense with zero filler, though the return-value details are somewhat redundant given an existing output schema.

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 two-parameter mutation with annotations and an output schema, the description covers input semantics, behavioral rules, and auth requirements adequately. The return-field explanation (vote_count, upvote_count, downvote_count) is redundant against the output schema but not harmful.

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?

With schema coverage at 0%, the description carries the burden and does so fully for `value`, spelling out the meaning of 1, -1, and 0. `developer_request_id` is left implicit, relying on its self-explanatory name and schema pattern, which is the only gap.

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 operation (voting) on a specific resource (a developer request's vote), with the three value semantics enumerated. It is clearly distinguishable from the sibling vote_post without opening a schema.

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?

It establishes clear context for when to apply each value (1 upvotes, -1 downvotes, 0 removes) and the one-vote-per-identity constraint. It stops short of naming an alternative tool or explicit exclusion conditions, but a caller can infer the intended use confidently.

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