Search intercity taxis

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

Annotations already cover the read-only/idempotent/non-destructive profile, and the description adds genuinely new behavior: whole-car capacity (up to 3 passengers), one offer per pick-up slot, price_toman is for the whole car not per person, and the shape of the `classes` summary. It does not cover pagination or auth requirements, so not a 5.

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?

Purpose and the pricing model are front-loaded in the first two lines, with the caveats about empty results and the city-id prerequisite following efficiently. Slightly fragmented layout but no wasted sentences.

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?

For a 7-parameter search with a full output schema and complete annotations, the description supplies the extra context an agent needs: capacity, per-car pricing, empty-result behavior, and the companion tool for city ids. Output format details are rightly delegated to the output schema.

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% – every parameter (date, limit, origin, car_class, depart_after/before) is already documented in the schema. The description's price and classes notes relate to the response, not to parameter syntax or meaning, so baseline 3 applies.

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 opening sentence states a specific verb+resource: private door-to-door intercity taxis for a date, whole car up to 3 passengers, one offer per pick-up slot. This distinguishes it from the bus, train and flight search siblings by mode and by capacity/pricing model.

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?

It gives a clear prerequisite (city ids must come from mb_find_place(mode='taxi')) and warns that many city pairs return no taxis. It stops short of explicitly saying when to prefer this over mb_search_buses/trains for the same route, so it is clear context without full alternative routing.

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