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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower; the description still adds meaningful context by noting the poll is public and that responses are operator-weighted aggregates. The warning that percentages are not event probabilities is a substantive data-semantics disclosure not present in any structured field. It stops short of describing freshness, caching, or behavior when the poll id does not exist.

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?

One front-loaded sentence with the resource first and the disambiguating caveat second; every clause carries information and nothing is padded.

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?

An output schema exists, so return values needn't be explained, and annotations cover the safety profile. However, for a retrieval tool the description leaves the identifier format and the relationship to list_polls/get_poll_format unaddressed, which is a real gap in an otherwise tidy definition.

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 0% for the single required parameter poll_id, so the description carries the burden — but it says nothing about the expected identifier format (numeric, slug, UUID) or whether it must reference a public poll. The word 'public' hints at a constraint but gives no actionable detail.

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 ('Read') and resource ('a public poll and operator-weighted aggregate responses'), so the agent knows this fetches poll data plus aggregates. It doesn't name sibling tools like list_polls or get_poll_format, so differentiation is inferred 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?

There is no statement of when to use this versus list_polls (enumeration) or get_poll_format (formatting). The caveat 'percentages are not event probabilities' is interpretive guidance, not usage routing, so the agent must infer selection from the name alone.

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