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

Annotations already declare readOnly/idempotent, so the description adds higher-value context instead of repeating them: the season appears only in the availability grid and shifts when the next season releases, each slot has its own cutoff so a future date is not necessarily live, and closed_cells must be skipped. This is real behavioral disclosure an agent could not infer.

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?

Front-loaded and information-dense, but the middle paragraph about next_release_at and AlertCamp polling the drop is tangential to this read tool and inflates the definition. Some sentences explain alert mechanics rather than how to call this tool.

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 an output schema present, the description needn't document return values, yet it still explains the non-obvious fields (max_span_days, closed_cells). A single-parameter read tool is fully specified: what it returns, why it's needed, and what to do with closed_cells.

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 coverage is 100% and there is a single parameter; the schema already states zone_id comes from list_campground_zones on DayUse parks. The description restates the DayUse precondition but adds no new format or derivation detail, 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 ('the dates a DAY-USE grid offers') plus the concrete return fields (start/end, max_span_days, closed_cells). It is clearly distinguishable from siblings like list_zone_sites and create_alert without opening any schema.

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?

Explicitly says 'Call this before setting day_use_cells' and explains why (the season is not exposed anywhere else in the provider's API). It also routes the agent to list_zone_sites for next_release_at, giving a clear when-to-use and an alternative.

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