Iconic CLS

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

Beyond the annotations, the description discloses major real-world behavior: no account is required, the car is held for 30 minutes, the trip confirms only after payment lands, the agent cannot self-serve payment, and change/cancel channels are provided. This is exactly the kind of operational context that annotations alone do not 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?

The description is front-loaded with the core purpose and maintains a logical flow: booking, hold, payment, instruction to hand over the link, then post-booking contacts. It is somewhat dense, especially the second sentence, but every sentence earns its place given the complexity of the workflow.

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 19-parameter booking tool with no output schema, the description covers the critical workflow: real booking, hold window, external payment link, confirmation trigger, and post-booking support. It does not spell out the exact return payload shape or edge cases like an expired payment link, but it is complete enough for the agent to act effectively.

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?

The input schema already covers all 19 parameters with descriptions and enums, so the parameter-semantics burden is largely met by the schema itself. The tool description does not add specific parameter-level meaning beyond that, so a baseline 3 is appropriate.

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 opens with "Place a real booking with no account," which is a specific verb plus resource and clearly distinguishes this tool from its siblings list_services and quote_trip. The subsequent details about the 30-minute hold and payment link reinforce that this is the actual booking action, not a quote or lookup.

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 explicitly instructs the agent to "Quote it first so you can tell them the price," implying quote_trip should be called before book_trip. It also warns that the agent cannot complete the payment and must hand the link to the person. It does not explicitly name alternatives or say when not to book, but the workflow guidance is clear enough.

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

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

Annotations already mark readOnlyHint=true and destructiveHint=false, so the description isn't burdened with safety disclosure. It adds valuable context about the tool's contents (pricing needs, coverage areas) and notes that a human books, implying manual steps. It does not contradict annotations.

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?

Two sentences with no filler. The first sentence packs the core purpose and scope, while the second provides a clear action directive. Every word 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?

For a zero-parameter reference tool without an output schema, the description covers all essential aspects: what it lists, when to use it (before quoting), and how it relates to the sibling tool. The absence of output format details is acceptable given the simple informational nature.

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?

With zero parameters and 100% schema coverage, there is nothing to explain about parameters. The description appropriately focuses on the informational value rather than parameter details, matching the baseline for parameterless tools.

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 the tool lists what Iconic CLS runs, including pricing prerequisites, covered airports/private airfields, and where human booking occurs. This distinguishes it from the sibling tool 'quote_trip' by specifying its informational scope.

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 explicit instruction 'Read this before quoting' directly tells the agent when to use this tool relative to the 'quote_trip' sibling. It also enumerates the content areas covered, making it clear it serves as a prerequisite reference.

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

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

Annotations already declare readOnlyHint and destructiveHint, so the safety profile is covered. The description adds valuable context by stating 'nothing stored' (non-persistence), 'estimate' (not guaranteed), and the distinction between standard and negotiated rates, going beyond the annotations.

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 three sentences long, front-loaded with the primary purpose. Each sentence contributes meaningful info: the output type, the conditions (standard rates, no account, nothing stored), and the estimate caveat. There is no redundancy or filler.

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 12-parameter tool with no output schema, the description clearly communicates the core response (single total) and gives important context (standard rates, estimate nature). It does not explain conditional parameters or return format details, but the schema handles parameter guidance. Sufficient for tool selection and basic invocation, though not exhaustive.

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 descriptions provide 100% coverage for all 12 parameters, so the baseline is 3. The description does not discuss any parameter specifics; it only mentions that the total includes the Operations & Chauffeur Fee, which is not tied to a specific parameter. Thus, no additional semantic value is added over 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 states a specific verb ('Price') and resource ('one trip'), and clearly defines the output as a single fixed all-in total. It distinguishes itself from the sibling tool list_services by focusing on pricing rather than service definitions.

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?

Provides clear context by stating 'Standard rates, no account needed, nothing stored', indicating when this tool is appropriate. However, it does not explicitly mention alternatives like list_services or exclusions for negotiated-rate accounts, leaving the when-not guidance implicit.

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