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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), so the bar is lower. The description adds useful data-coverage context by naming Parks Canada day use and Recreation.gov permit areas as included sources, but does not disclose anything further about volume, pagination, or how the aggregated sources behave.

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, no wasted words, and the scope statement is front-loaded before the conceptual clarification. Slightly fragmentary opening (no leading verb) but efficient overall.

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, annotations covering safety, and a single fully documented parameter, the description only needs to frame scope and the campground/zone/site model — which it does. A pointer to the downstream zone/site tools would make it fully complete, but nothing needed to call it correctly is missing.

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% for the single park_id parameter, so the schema already documents the only input. The description adds no syntax, format, or identifier guidance beyond what the schema provides, making the baseline 3 appropriate.

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?

The description states the resource and scope ('Campgrounds within a park') and adds domain semantics — a campground is what an alert watches, while zones and sites are the bookable inventory — which helps separate it from list_campground_zones and list_zone_sites. It lacks an explicit verb in the description body, but the title supplies 'List', leaving the purpose unambiguous.

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 hierarchy note ('its zones and sites are the bookable inventory') hints that an agent should call this before drilling into zones/sites, but no condition or alternative is named explicitly. There is no when-not guidance and no direct pointer to list_campground_zones or list_zone_sites.

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