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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true, destructiveHint=false), and the description adds genuinely non-obvious behavior: the returned availability is a live hint and the authoritative status is re-confirmed at checkout. That tells the agent not to treat the result as a booking guarantee. No rate limits or auth requirements are mentioned.

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?

Two short sentences, zero waste, with the core purpose front-loaded and the caveat immediately after. Every sentence earns its place.

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, open-world availability check with no output schema, the description conveys enough: what is checked, the date scoping, and the reliability caveat. It stops short of describing the shape of the availability response (e.g. boolean vs. slot list), which would be the only remaining gap.

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% and the schema already documents the id pattern, the date formats/relative terms and default, and the locale's localization-only role. The description adds no parameter-level detail beyond that, so the baseline 3 applies.

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 ('Check') and resource ('DayPass experience availability') plus the scoping input (a given date). It is clearly distinguishable from siblings like search_experiences or get_experience, though it never explicitly routes away from the closest alternative, get_quote.

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: the note about re-confirmation at checkout hints this is a pre-booking sanity check, but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g. get_quote for firm pricing/booking status).

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