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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new behavior: the 30-day horizon, park-local time semantics, and the important caveat that results are estimates, not guarantees.

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 sentences, front-loaded with the usage condition and followed by return description; the estimate caveat is concise. Slightly dense with multiple clauses packed into the second sentence, but no wasted 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?

No output schema exists, so the description carries the return-value burden and does it well: hourly predicted waits with bounds, weekday typical waits, and best/worst windows in park-local time. Only missing minor details such as what happens when a date has no data or whether waits are per-ride or per-park.

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 ride_id and date are already documented in the schema including the 30-day limit, today default, and ID provenance. The description only restates the 30-day window and ID resolution step, adding little beyond the schema.

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?

Names a specific verb+resource ('best time to ride') and frames the intent concretely: avoiding long waits on a given day. The 'hourly predicted waits' framing implicitly separates it from parky_get_waits (actual waits), but no sibling is named explicitly, so an agent must infer the boundary.

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 a clear trigger ('when a visitor asks when to ride something to avoid long waits') and bounds the context to a specific day within 30 days. It also states a prerequisite ('Resolve the ride ID first') although it does not name parky_find_experience or state when NOT to use this (e.g., for current waits).

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