search_reservations

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

No annotations provided, so description carries full disclosure burden. It doesn't explain what happens when filters are omitted, how the date range logic works (arrival vs departure windows), pagination behavior, or result ordering. The presence of an output schema reduces some burden, but input behavior remains undocumented.

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?

Single sentence, front-loaded with action verb, no redundant phrases. However, extreme brevity is inappropriate given the tool's complexity (9 parameters with zero schema documentation), making it overly terse rather than efficiently concise.

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?

Inadequate for a 9-parameter search tool with zero schema descriptions and no annotations. Missing critical semantics for date range parameters (which have start/end variants), unmentioned guestEmail parameter, and no explanation of the limit parameter despite its behavioral impact on 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?

With 0% schema description coverage, the description must compensate but falls short. It implicitly covers 7/9 parameters (grouping 4 date fields as 'date range') but completely omits 'guestEmail' and 'limit'. It also fails to explain date formats, exact vs partial matching rules, or that date ranges require paired start/end 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 ('Lookup') with clear resource ('reservations') and lists searchable dimensions (guest name, date range, listing, reservation id). However, it doesn't explicitly differentiate from sibling 'get_reservation_brief', which also retrieves reservation data.

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?

No guidance provided on when to use this versus 'get_reservation_brief' or other siblings. Doesn't mention that all 9 parameters are optional (0 required) or how to combine filters effectively.

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