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

Goes meaningfully beyond the annotations: it discloses that availability is re-checked at creation time, that no tee time is actually booked (consistent with destructiveHint=false), that the result is a shareable link, and that the option limit is eight. It leaves out access control (who can vote) and any poll lifetime/expiry behavior, which are the main remaining unknowns for an openWorldHint mutation.

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?

Three short sentences, front-loaded with the action, each carrying distinct information (creation scope, availability re-check, non-booking caveat, delivery of a voting link). No filler.

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 mention of 'the returned link' is exactly the return-value information an agent needs, and the non-booking caveat clarifies the mutation's side effects. The gap is the uninterpreted option fields, which matter for constructing a valid call.

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% and the description provides essentially no parameter meaning: it restates the max of eight options (already in maxItems) but never explains courseId, date, minute (0-1439, presumably a time-of-day offset), or the 9/18 holes enum. For a 1-param tool whose single param is a nested object with four undocumented fields, the description should compensate and does not.

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 and resource ('Create a shareable tee-time poll') plus scope ('from up to eight search options') and an explicit boundary ('this does not book a tee time'), which cleanly separates it from a booking action and from get_tee_time_poll's retrieval role.

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 implied rather than stated: 'Friends vote at the returned link' signals the scenario, and 'search options' hints the inputs derive from a search tool, but it never says when to prefer this over alternatives such as reading an existing poll with get_tee_time_poll or when not to create one.

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