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

With no annotations present, the description carries more weight. It does disclose that prices are fixed and lists service components, but it does not clarify return format, currency, whether the optional chauffeur transfer affects price, or any limitations. This is partial transparency but not full.

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 states the purpose first and then provides useful parenthetical details about the service inclusions. It is compact and avoids redundancy, though slightly dense due to multiple parenthetical clauses.

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?

Without an output schema, the description should explain what the tool returns, but it only says prices are fixed. It also does not address the language parameter or clarify how the optional chauffeur transfer affects pricing. An agent would still be uncertain about the exact response and edge conditions.

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 67% and the description adds meaning by explaining what the vip-meet-greet and student-pickup service values refer to, including the Heathrow-specific service details. However, it adds no information about the guests or language parameters, leaving part of the semantics to the schema.

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 states that the tool returns fixed prices for two specific services: Heathrow VIP Meet & Assist and student/unaccompanied-minor pickup. It is specific enough to distinguish from the sibling pricing tools by service type, but it does not explicitly contrast itself with get_transfer_price or get_hourly_price.

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?

Usage is implied by the service names and scope: Heathrow VIP Meet & Assist and student pickup at London airports. However, the description gives no explicit guidance about when to choose this tool over sibling pricing tools, and no 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.