search_tours

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

With no annotations, the description carries the behavioral disclosure burden. It clearly states that the tool is public and does not require an API key, which addresses authentication expectations. The 'Search' wording implies read-only behavior, but it does not describe the return format or what happens when no filters are provided.

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?

The description is two short sentences with the core action front-loaded. Every sentence earns its place, and there is no redundant filler.

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?

The description is adequate for a simple search tool and covers public access and authentication. However, the schema marks both parameters as optional while the description says 'by location and date,' leaving ambiguity about calling with zero parameters. The absence of an output schema also means return behavior is left implicit.

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 fully documents date and location. The description only restates that searches happen by location and date, adding no additional meaning about formats, defaults, or the optionality of the parameters.

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 uses a specific verb ('Search') with a clear resource ('public tours and experiences') and the two key filters (location and date). It is easily distinguishable from sibling tools like check_availability and create_booking_hold, which imply later workflow steps.

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?

The description gives useful context: the tool is public and requires no API key. However, it does not explicitly say when to use this tool versus check_availability or create_booking_hold, nor does it mention that location and date are optional despite being the described search criteria.

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