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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered structurally. The description earns extra credit by adding domain behavior: fixed per-vehicle pricing, the rule that a 7th passenger requires a second vehicle, and the Istanbul side-pricing model, none of which the annotations convey.

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?

Information-dense and front-loaded: market coverage first, then pricing model, then filters, then the read-only guarantee. It is telegraphic and slightly list-like, but essentially no sentence is wasted.

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?

With an output schema present and rich annotations, the description only needs to carry domain semantics, and it does: markets, airports, pricing basis, and the side/district coupling. The one missing piece is an explicit hand-off to quote_transfer for price quoting or booking.

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 already 88%, so the baseline is 3. The description goes beyond it by explaining the side/district relationship ('priced by hotel side (pass district or side)') and the passenger capacity constraint, both of which clarify how parameters interact rather than merely restating enum values.

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 states a specific domain and resource (private transfers, fixed price per vehicle) and enumerates the two markets it covers, Dubai and Istanbul, with their airports. It does not, however, contrast itself with the sibling quote_transfer, which is the closest alternative for transfer pricing, so the agent must infer the split.

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 lists the filterable dimensions (airport, serviceType, direction, side, district, passengers) and notes the read-only nature, which gives implied usage context. But it never states when to reach for this tool versus quote_transfer or search, so the routing decision is left to inference.

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