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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint), so this dimension is about added context. The description contributes that results include reservability, a booking link, and the campground's own page to read conditions next, which is genuinely useful output-shape context. It says nothing about result limits or error behavior.

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?

Three front-loaded sentences, each carrying distinct load: capability/scope, when to call it, and what comes back. No filler or restatement of the name.

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 takes on return-value disclosure and does so well (reservable flag, booking link, campground page for follow-up), and annotations cover the safety profile. It is slightly thin on result volume or pagination expectations for a radius search, but nothing needed to invoke correctly is missing.

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%, so the schema already documents latitude, longitude, radius default/max, and reservable_only defaults. The description only paraphrases the coordinate-and-radius concept and adds no format or edge-case detail beyond the schema. Baseline 3 applies.

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 states a specific verb and resource with scope ('Find campgrounds within a radius of a coordinate across federal, state and private land') and even names what it returns (reservable status, booking link). It does not explicitly name its siblings find_trails or check_conditions, so sibling differentiation is only implied by the tool name.

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?

'Call this when someone asks where to camp near a place' gives a clear triggering condition for the agent. No exclusions or explicit alternatives (e.g., a nearby-place vs. named-campground search) are offered, so it stops short of full routing guidance.

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