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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety and idempotency profile is fully covered. The description adds the limited extra context that results are federal recreation areas, but says nothing about pagination, result size, or matching behavior beyond what annotations already imply.

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 tight sentences, zero filler. The resource scope is front-loaded before the sibling-routing sentence, so the most important selection cue comes first.

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 whose annotations cover the safety profile and whose four simple parameters are fully described in the schema, the description supplies what an agent needs to select it. Since no output schema exists, a sentence on return shape or pagination would have made it fully complete.

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 every parameter (limit, query, state, activity) is already documented in the schema. The description echoes the same three filter dimensions (name, state, activity) but adds no syntax, format, or matching semantics beyond it; baseline 3 is correct.

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 resource (federal recreation AREAS) and immediately defines the granularity with concrete examples (whole national forest, park unit, BLM management area). It also names the sibling it is meant to be distinguished from, so an agent can place it correctly without opening either 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 routes between this tool and recreation_search_facilities: higher-level place search here, specific facilities (campgrounds, trailheads) there. This is exactly the when-to-use/when-to-use-something-else guidance the dimension asks for.

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