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

Annotations already declare the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), so the description carries a lower behavioral burden. It adds agency/facility-type scoping context but discloses no additional behavioral traits such as pagination, result count, or output shape. Nothing contradicts the annotations.

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 action verb, and zero filler. The first sentence covers what is searched and across which agencies; the second covers all filter dimensions; every clause 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 search tool, the description plus 100%-covered schema and rich annotations together supply what an agent needs to invoke it correctly. The only notable omissions are explicit sibling routing and an undocumented return shape, though no output schema exists to compensate for the latter.

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 every parameter (limit, query, state, activity) already has a clear description, so the baseline is 3. The tool description adds marginal value by citing concrete activity examples (CAMPING, FISHING, HIKING) that reinforce the schema's 'etc.', but introduces no new semantic information.

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?

Opens with a specific verb+resource ('Search US federal recreation facilities') and enumerates both facility types (campgrounds, picnic areas, trailheads, marinas, visitor centers) and managing agencies (NPS, USFS, BLM, USACE, BOR, FWS), making the scope unmistakable. The breadth of the search also implicitly distinguishes it from the campsite- and rec-area-specific sibling tools.

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?

The description implies usage by listing facility types and filter dimensions, but never states when to prefer this tool over recreation_search_campsites, recreation_search_recareas, or recreation_facility_detail. With four recreation siblings present, the absence of explicit when-to-use or when-not-to guidance is a real gap.

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