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

Annotations already declare readOnly/openWorld/non-destructive, so the safety profile is covered. The description adds real domain behavior beyond that: NPS status derives from the park's published schedule, Forest Service status from each forest's list refreshed every 6 hours, and 'not listed' is explicitly defined as unknown rather than closed. That is meaningful interpretation guidance.

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?

Front-loads the core capability and the follow-up-tool pointer, then uses the remaining space for status semantics. The status paragraph is dense but each clause carries distinct information; no filler.

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 explain the interesting return content (open-today flag, booking link, ids). It is nearly complete, though it omits pagination/limit behavior for a search that defaults to 25 and caps at 100.

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 only 33%, and the description largely mirrors the query parameter semantics already in the schema. It adds concrete value examples for query but says nothing about limit or open_today_only, so the low-coverage params remain 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?

States a specific verb (Find) and resource (NPS/Forest Service campgrounds) and enumerates the accepted lookup keys, including concrete examples. It also names the downstream sibling campgrounds_get_status, so an agent can distinguish it from the other campground tools without opening schemas.

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 creates a clear chain to campgrounds_get_status for id-based follow-ups, which is useful routing. However, it never explains when to prefer this over campgrounds_find_near or nationalparks_find_campgrounds, so usage is implied rather than stated.

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