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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description reinforces and extends this: 'we never book on their behalf, never hold sites, never take payment' explains WHY the operation is read-only and idempotent. 'Deterministic' and 'pre-filled' add behavioral specificity about output consistency that annotations cannot express. No contradiction 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?

Two sentences, zero filler. The core function and scope boundary are front-loaded in the first sentence; the second sentence delivers routing guidance. The parenthetical about never booking/holding/paying is dense with behavioral information without bloating length.

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?

For a straightforward link-generation tool with rich annotations covering the safety profile, the description provides the essential contract: what is returned (a deterministic, pre-filled link), the usage context, and the behavioral boundaries. Minor gaps exist — no detail on return format beyond 'link', no guidance on how the optional 4 parameters affect the output, and no fallback behavior for ambiguous park names — but none are critical for correct invocation.

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 57% — category, start_date, and end_date have no schema descriptions, and the description doesn't compensate for those. However, it does add cross-parameter meaning by explaining that park, dates, and equipment get embedded/pre-filled into the resulting link, which is coordination knowledge the schema fields individually don't convey. This is adequate but doesn't fully close the documented-parameter gap.

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 names a specific deliverable — a deterministic link into the official reservation system with park, dates, and equipment pre-filled. This clearly differentiates it from all six siblings (alerts, weather, availability, info, campsite search), none of which generate a booking link. The phrase 'the user completes the booking there' crisply defines the tool's scope.

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?

'Use after a search, or when the user already knows the park and dates' gives explicit invocation conditions. The description also states what the tool is not for — booking, holding sites, or taking payment — which routes the agent away from expecting transactional behavior. It doesn't name sibling alternatives explicitly, but the boundary it draws is clear enough.

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