search_availability

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

Discloses important behavioral details: start_date inclusive, end_date exclusive (night not required), and optional site_ids. Without annotations, this covers key traits. Return format is likely covered by output schema.

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?

Very concise: a clear one-line purpose, usage examples, and a structured args list. Every sentence adds value with no waste.

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?

Covers the core behavior for a search tool with 3 parameters. Output schema exists, so return values are documented elsewhere. Could mention pagination or result size, but not essential given the tool's simplicity.

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?

Adds significant meaning beyond the bare schema (which has 0% description coverage). Explains ISO date format, inclusivity/exclusivity, and the purpose of site_ids with an example of omission.

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 states the tool finds campsites available across a date range, with a specific verb and resource. It distinguishes from sibling tools like list_sites (which lists sites) or get_reservation (specific reservation).

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?

Provides example natural language queries (e.g., 'is there anything open July 4-7?') and explains optional site_ids scoping. However, it does not explicitly mention when to use this over alternatives like list_sites or list_reservations.

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