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

Annotations already declare readOnly/non-destructive/closed-world, and the description still adds real context beyond them: it excludes booker identity ('never who booked it'), defines what 'stuck' means and which tool fixes it, limits bookings to 30 days ago or later, and notes that times are in the zone captured at creation.

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 purpose is front-loaded and nearly every clause carries new information, so little is wasted. However, the whole thing is a single comma-spliced run-on that mixes per-link fields, per-poll fields, booking-page fields, and booking history in one breath, making it harder to parse than it needs to be.

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 must carry the return-shape burden and it does: it enumerates link, poll, booking-page, and booking fields, explains sort orders (oldest first for links, most answers first for polls), and covers the stuck-state edge case and timezone semantics.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description's field enumeration describes output, not inputs, which is appropriate here.

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?

Opens with a specific verb plus both resources and a scope filter ('booking links and group polls still open or being booked'), then enumerates the exact fields returned for each. It also names the neighboring tools (links_polls_close, polls_results) so an agent can distinguish this from them without opening schemas.

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 clearly implied by the 'still open or being booked' filter and reinforced by routing to alternatives: links_polls_close for stuck entries and polls_results for answers. It does not state explicit exclusions (e.g., closed links or past bookings are out of scope), which keeps it short of a 5.

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