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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds only 'NPS public domain' (licensing) which is not behavioral. No mention of pagination behavior, data freshness, or rate limits beyond what annotations 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?

The description is a single sentence listing attributes but lacks structure. It is concise (no wasted words) but could be more informative by including a verb (e.g., 'List' or 'Search') and mention of pagination or default behavior.

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 5 optional parameters, an output schema, and many sibling tools, the description is too brief. It does not state what type of data is returned (e.g., list of campgrounds) or how results are ordered. The presence of an output schema slightly reduces the burden, but the description still feels incomplete for a tool with multiple filtering options.

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 each parameter (state_code, park_code, q, limit, start) having a clear description. The tool description adds no additional parameter context beyond the schema, so baseline score of 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 clearly states the tool provides NPS campground information including reservation info, accessibility, amenities, and coordinates. It distinguishes itself from sibling tools like travel.nps.parks and travel.nps.alerts by focusing specifically on campgrounds.

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?

No guidance on when to use this tool versus other NPS tools or how to choose between parameters. The description does not mention filtering strategies or that multiple optional filters can be combined.

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