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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description adds the useful handoff detail that provider and slug feed downstream availability/alert calls, but says nothing about pagination, result caps, or coverage limits.

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 short sentences, zero filler, with the scope statement front-loaded before the downstream handoff hint. Every clause earns its place.

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?

An output schema exists so return values need no explanation, and the description does cover the downstream workflow. But with five undocumented parameters and cursor-based pagination, an agent still lacks guidance on how to page or shape results.

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 0% across five parameters (q, limit, state, cursor, provider), yet the description explains none of them. It names "provider" as an output field to reuse but gives no meaning, defaults, or usage for limit, state, cursor, or the free-text q.

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 (Search) and resource (CampWatch's supported Australian campground catalogue), which is distinctive among siblings. However, it does not explicitly contrast itself with list_providers or the alert tools, so the agent must infer the boundary.

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 returned provider and slug for availability and alerts" tells the agent what to do with the results, implicitly routing to check_availability and create_alert. There is no explicit when-not-to-use guidance, but the workflow context is clear.

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