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

Annotations already declare readOnly/non-destructive/no open-world, so the safety profile is covered. The description adds real behavioral context beyond that: result ordering (open, then closed in the last week), that each option carries voter attribution including would-sit-out, and that a winner appears once closed — including a non-obvious time-window filter on closed polls.

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?

A single dense sentence, front-loaded with the resource and ordered return shape, with no filler. It is slightly run-on with stacked clauses ('who picked it and who would sit it out'), but every clause carries information an agent can use.

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?

For a read-only, one-required-parameter tool with full schema coverage and an output schema, this description supplies ample context: what is returned, in what order, and what the id references mean. It could go further by explicitly excluding the date-poll and answer paths, but nothing essential is missing.

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% for the single tripId parameter, so the schema fully documents it (uuid, from list_trips). The description adds nothing about tripId semantics and instead references get_trip for people ids, which pertains to output rather than input.

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 names a specific resource (polls/questions asked of the group) and scopes it precisely: open polls first, then those closed in the last week, with voters and winners. It does not explicitly distinguish itself from close siblings like get_date_poll or ask_poll, so the agent must infer the boundary from the verbs.

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 description of returned content; there is no explicit 'use this when' or exclusion against get_date_poll, ask_poll, answer_poll. The single chaining hint ('People are by id, from get_trip') tells the agent what to call next, not when to call this tool.

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