NPS Campgrounds

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint, so the tool is understood as a safe read operation. The description adds only the data source ('NPS public domain'), not behavioral details like pagination or rate limits, so it meets the baseline for a tool with annotations.

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 very short (one sentence) and front-loads key content. The phrase 'NPS public domain' is slightly extraneous but does not detract much. It could be more structured with an explicit verb.

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 five optional parameters with search and pagination capabilities, the description is incomplete. It does not explain how to combine filters (e.g., comma-separated values) or use limits and offsets. The presence of an output schema does not excuse the lack of usage context.

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 descriptions cover 100% of parameters (state_code, park_code, q, limit, start), so the description adds no extra meaning. It mentions output attributes (reservation info, etc.) but does not map them to parameters, adding marginal value.

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 indicates the tool returns NPS campgrounds with key attributes (reservation info, accessibility, amenities, coordinates), distinguishing it from siblings like travel.nps.parks or travel.nps.things_to_do. However, it lacks an explicit verb like 'list' or 'search', making it a noun phrase.

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 provides no guidance on when to use this tool versus alternatives, such as searching by park vs. state, or using the free-text query. There is no mention of when not to use it or what data is excluded.

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