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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the authorization constraint and the anonymity guarantee ("Never says who voted for what"). That anonymity note is genuinely non-obvious behavior an agent cannot infer from structured fields, though error behavior and results-availability timing are still unstated.

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 short sentences with zero filler, front-loading the payload and then the two constraints that matter most (access and anonymity). Nothing could be removed without losing information.

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 must carry the return shape, and it does: per-option counts, total ballots, and open/closed status, plus a privacy caveat. It is nearly complete for a two-parameter read tool, missing only what happens when the vote has no ballots yet or the caller lacks organizer rights.

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 both parameters are already documented, including the "latest when absent" default for voteId. The description adds no additional semantics about parameter format or resolution (e.g. name-vs-id collision behavior), 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?

The description gives a specific verb and resource ("Reads a vote's counts per option") and enumerates the payload (counts, total ballots, open/closed state), which separates it from the mutating siblings event_vote_open and event_vote_close. It stops short of naming those siblings, so the differentiation is implied by the verb rather than explicit.

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?

"Hosts and organizers only" is a useful access precondition, but there is no guidance on when to reach for this versus event_vote_open/event_vote_close, no prerequisite (e.g. a vote must exist), and no note on how to discover a voteId. Usage is only implied by the described output.

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