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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuine value beyond that by enumerating the returned payload (options, votes, reasons, vote-change history) and by disclaiming that the output does not certify transcript reads or approve decisions, which prevents an agent from over-reading the result.

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?

Two sentences, front-loaded with the return contents and no filler. The second sentence is compact but uses undefined jargon ("attest transcript reads") that costs a little clarity relative to its length.

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 carries the burden of describing return values and does so concretely. For a one-parameter, fully documented, read-only listing tool this is essentially complete, with only the missing sibling routing leaving a small gap.

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?

There is a single parameter and schema description coverage is 100%, with room_id already documented as OAuth-authorized and pattern-constrained. The description adds no further meaning about room_id, 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 uses a specific verb ("Returns") with a precise resource enumeration: poll options, current votes, reasons, and vote-change history, plus attribution. An agent can tell this is a read of poll state rather than a vote or a result submission, though it never names the siblings vote_poll or propose_poll_result that operate on the same resource.

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?

Usage is only implied by the read-oriented framing; there is no explicit "use this when you need X, use vote_poll instead when Y" routing despite three sibling tools touching polls. The negative clause ("Does not attest transcript reads or approve decisions") sets a boundary but is a scope disclaimer rather than when-to-use guidance.

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