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

Annotations already establish read-only, open-world, non-destructive behavior, so the bar is lowered, and the description still adds real value: data freshness (Forest Service statuses refreshed every 6 hours), the source of each agency's open/closed determination, and the meaning of the ambiguous 'not listed' value. It does not cover rate limits or result ordering beyond 'nearest'.

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?

The core capability and return fields are front-loaded in the first sentence, and the following sentences earn their place by disambiguating status semantics. Slightly dense, but no filler or repetition.

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 no output schema, the description does the work of naming the returned fields (distance, open today, booking link) and explaining status provenance and freshness. Gaps remain around distance units, result limiting, and what happens when nothing falls within the radius, but the essential contract is conveyed.

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 0% across 5 parameters, so the description carries the full burden. It names latitude/longitude and implies open_today_only via 'whether each is open today', but says nothing about limit or max_km (radius in km, defaults, caps), leaving two filters completely undocumented.

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 gives a specific verb+resource (find campgrounds) plus a precise scope: nearest a latitude/longitude across NPS and Forest Service lands. It clearly reads as a proximity search, but it never distinguishes itself from the similarly named sibling nationalparks_find_campgrounds or campgrounds_search, so the agent must infer the split.

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 by the geographic framing ('nearest a latitude/longitude'), which tells the agent this is the proximity path rather than a name search. However, there is no explicit when-to-use statement, no exclusions, and no pointer to the sibling tools it overlaps with (campgrounds_search, nationalparks_find_campgrounds).

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