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

Annotations already declare this as a read-only, non-destructive, non-open-world operation, so the description gets credit for adding substantial behavioral context beyond that. It explains what a booked or closed poll returns, what the booked field means, and that times use the poll's stored timezone. The only gap is that it does not mention permission or error behavior.

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 description is front-loaded with its main purpose and every sentence carries information about behavior or output shape. It is somewhat dense and cryptically phrased in places, but it is not padded or redundant.

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 responsibility for explaining return values, and it does so by describing upcoming times, respondent addresses, answer status, ordering, and booking behavior. Some phrases such as "most first" and "each address it is for" remain slightly ambiguous, but the overall context is sufficient for a simple read tool.

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%, so the schema already documents the single poll UUID parameter, including that it matches the id from polls_create. The description does not add syntax or formatting detail beyond that, so the baseline of 3 is appropriate.

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 opens with a specific verb and resource: "Read a poll's answers." It also previews the returned structure (upcoming times, addresses, answer status), making the purpose clear. It does not explicitly contrast itself with siblings such as polls_book or links_polls_close, so it falls short of a 5.

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 explicit guidance on when to use this tool versus alternatives such as polls_book, polls_create, or links_polls_list. The note that a booked or closed poll holds no answers is useful behavioral context, but it is not framed as a selection rule or exclusion condition.

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