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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: queries hit live reservation systems in real time and cover 30+ named providers, which tells an agent this is a network-dependent lookup with provider-dependent coverage. It omits latency/rate-limit and failure behavior, so not a 5.

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, purpose front-loaded in the first, with the provider detail second. Efficient overall, though the provider enumeration is slightly broader than strictly necessary for invoking the tool.

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 a complete input schema, an existing output schema, and rich annotations, the description is sufficient to call the tool correctly. Minor gaps remain around sequencing with siblings and behavior on unavailable/unrecognized campground IDs, but nothing essential 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%, with formats, defaults, and ranges documented for campground_id, start_date, end_date, and min_nights. The description adds nothing parameter-specific, so the 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?

States a specific verb and resource ('Check real-time campground availability') plus the scoping constraint ('for specific dates'), which is clearly distinct from siblings like search_campgrounds or get_campground_details. It never names an alternative tool explicitly, so it stops short of full sibling differentiation.

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?

Usage is implied by 'real-time availability for specific dates,' and the provider list hints at the domain of applicability, but there is no explicit when-to-use vs alternatives (e.g., search_campgrounds first, or prepare_reservation after). No exclusions or prerequisites are stated.

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