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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds real value: it discloses the agent-token auth requirement and the interpretive caveat 'votes are opinions, not proof'. It also hints at pagination.next_offset and version-conflict handling that the annotations do not cover.

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?

Three tight sentences, front-loaded with the core action and scope, then pagination guidance, then the auth/caveat note. Nothing is wasted.

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?

With no output schema, the description usefully names pagination.next_offset to indicate the return shape, and flags the token requirement and version semantics. It is nearly complete, though it could say more about what each event contains.

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 coverage is 100%, so the schema already documents limit, offset, api_key, version, and record_id including the version-conflict note. The description adds only marginal framing ('optionally for one version'), so the baseline 3 applies.

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?

States a specific verb and resource (read vote changes and reasons), clearly delimiting this from generic change history. It does not explicitly name the sibling read_change_history to disambiguate, so it is clear but lacks sibling routing.

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 phrase 'optionally for one version' implies when to scope to a version, and 'Follow pagination.next_offset' implies iterative reads, but there is no explicit when-to-use versus read_change_history or the voting siblings (upvote/downvote_information).

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