Best available rate

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

With no annotations provided, the description must carry the full behavioral disclosure burden. It states the core outcome (cheapest available rate) but does not disclose output format, error behavior, how optional parameters like date affect results, or any rate-specific details (taxes, currency, etc.).

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 a single, front-loaded sentence that immediately communicates the core purpose. No redundant words or filler; it 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?

Given no output schema and no annotations, the description should provide more context about return values or rate details. It also omits the adults/children parameters, which are likely relevant for rate calculation. The description is minimal and leaves significant gaps for a 4-parameter 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 only 25% (property only). The description adds the date format and optionality, which is helpful, but it fails to mention the 'adults' and 'children' parameters that are present in the schema, leaving their semantics unclear. The description does not sufficiently compensate for the low schema coverage.

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 identifies the resource (property) and scope (cheapest available rate, optional date), distinguishing it from get_rates by explicitly stating 'Cheapest'. However, it lacks an explicit verb, relying on the tool name for the action.

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 intended usage is implied (when you need the cheapest rate for a property) but the description does not explicitly state when to use this tool versus alternatives like get_rates or get_availability, nor does it provide exclusions or alternative recommendations.

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