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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine behavioral context beyond that: a 60-day coverage window and the explicit boundary that Parky cannot sell tickets, which prevents an agent from promising a purchase flow.

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 usage trigger, followed by what is returned and then the capability boundary. No filler and nothing buried.

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 carries the burden of describing the return and does so (on-sale/sold-out nights plus lowest price). Combined with full parameter coverage in the schema and complete safety annotations, an agent has everything needed to call this correctly.

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%, so all three parameters (resort, from, to) are already documented with defaults and limits in the schema. The description's 'Covers up to 60 days' restates the schema's 'at most 60 days in all' rather than adding format or syntax guidance, 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 and resource (ticketed event nights at a supported resort) and pins down the returned facts: which nights are on sale or sold out, and the lowest price. The named event examples (Mickey's Not-So-Scary Halloween Party, Jollywood Nights, Halloween Horror Nights) make it unmistakable against siblings like parky_get_ticket_prices and parky_get_showtimes.

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?

Gives an explicit trigger — 'Use this when a visitor asks about separately ticketed event nights' — which is a clear context for selection. It does not, however, name the alternative to use for general admission tickets or explain what to do when the resort isn't supported, so the routing guidance is good but not exhaustive.

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