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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds important context beyond that: it explicitly states the tool never reserves, charges, creates an intention, or sends a payment request, which is critical for an agent deciding whether to use this in a booking flow.

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 compact and front-loaded: it states the operation, then the return value, then the safety guarantee. Every sentence adds value and there is no repetition of schema details.

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 covers the core search behavior and safety profile well, and an output schema exists to describe return values. However, with many optional filter parameters and no mention of pagination or how to discover valid destinations (e.g., list_destinations), the description is not fully complete for a complex search tool.

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 low at 38%, so the description must compensate for undocumented parameters. It only mentions destination, dates, and guests, but leaves page, pageSize, bedrooms, language, price bounds, amenities, and categories unexplained. This is insufficient for a 13-parameter tool.

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 and resource: 'search of vacation homes' for availability and prices. It clearly distinguishes from siblings by indicating it is a multi-result search, versus get_home (single property) and list_destinations (destinations only).

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 clear context: use this when you need current availability, prices, and booking links for vacation homes by destination, dates, and guests. It does not explicitly name alternatives or exclusions, but the intended use case is evident.

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