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

Annotations already carry readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered and the bar is lower. The description adds one useful behavioral nuance beyond annotations: the granularity distinction that results are broad area units rather than facility-level records. It does not describe response shape or result-count behavior, so a 3 is appropriate given the strong annotation coverage.

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, both substantive and correctly front-loaded: the first scopes the tool with a verb, resource, and concrete examples, the second routes the agent to the sibling alternative. There is zero filler or repetition of schema content.

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 zero-required-parameter search tool with full schema coverage and safety annotations, the description covers the essential decisions: what can be searched and when to select this tool over the facilities sibling. The notable gap is that no output schema exists and the description does not hint at the result shape or behavior (e.g., what fields appear, how limit applies), which would help an agent set expectations.

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%, with all four parameters (limit, query, state, activity) already documented in the input schema. The description's 'by name, state, or activity' loosely maps to query/state/activity but adds no semantic detail beyond what the schema provides. Baseline 3 applies because the schema does the heavy lifting.

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 (Search) and a clearly scoped resource: federal recreation AREAS defined as broader units with concrete examples (whole national forest, national park unit, BLM management area). It also names the search dimensions (name, state, activity) and explicitly contrasts itself with recreation_search_facilities, enabling sibling differentiation without opening the 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?

Provides explicit routing guidance: 'For higher-level place search use this; for specific facilities (campgrounds, trailheads) use recreation_search_facilities.' This names the alternative and the exact condition that selects between the two tools, leaving nothing to inference. The only minor omission is not addressing other recreation siblings like recreation_search_campsites or recreation_nearby.

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