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

Annotations already establish this as a safe, closed-world read, so the burden is lower; the description still adds the non-obvious behavioral fact that the result is null when no date poll is active. It also decodes the answer semantics ("maybe" meaning "if I must"), which no annotation or schema field conveys.

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 a colon-delimited inventory of what comes back, plus a short null clause; nothing is padded. The trade-off is that it reads as a fragment and never states the retrieval verb outright, leaning on the title for that.

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 one-parameter read with an output schema and full annotation coverage, the description covers the applicable context, the shape of the result at a high level, and the null case. Nothing needed to call it correctly is missing, though it could note whether answers are attributed per participant.

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 with 100% schema description coverage, including its UUID format and origin ("from list_trips"), so the schema carries the load. The description adds no further meaning about tripId, which is acceptable at this coverage level.

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 the resource precisely (the trip's date poll) and enumerates its contents: suggested date ranges, each person's yes/maybe/no answer, and the current leader. That is clearly distinct from a general poll tool, though it never explicitly names the siblings it differs from (get_polls, answer_date_poll).

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?

"While the trip's dates are being decided" establishes the situation in which this tool is relevant, and "Null when the trip isn't asking" states the when-not case, so an agent knows an empty result is expected, not an error. It stops short of pointing at the alternative tools for answering or listing other polls.

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