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

Annotations already cover read-only and idempotent behavior. The description adds value by naming the returned fields (IDs, names, descriptions, phone, coordinates) and demonstrating a sample call. It does not go into pagination or rate limits, but for a read tool with safe annotations this is adequate.

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 plus an example deliver the core message with zero filler. The scope, filters, return fields, and a representative call are all front-loaded and easy to parse.

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?

Given the schema covers parameters and annotations cover safety, the description completes the picture by stating return fields and an example. No output schema exists, but the listed fields suffice for typical use. The only gap is not explicitly routing to sibling tools, but that is a refinement rather than a missing necessity.

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%, and the schema already documents each parameter including defaults. The description echoes 'query' and 'state' but adds no genuinely new parameter semantics beyond the schema, so a baseline 3 is 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 uses a specific verb ('Search') and resource ('US federal recreation areas'), clearly defined as parent regions containing campgrounds and facilities. This distinguishes it from sibling tools like search_facilities or list_campsites by scoping and hierarchy.

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 gives clear context about what is searched and returns, implying it is for parent-level recreation areas rather than individual facilities or campsites. However, it does not explicitly name alternatives like search_facilities or state when not to use it, so it stops short of a 5.

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