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

Annotations only indicate readOnlyHint=false and destructiveHint=false, providing minimal safety profile. The description adds meaningful behavioral context: the booking is created as 'pending', the operator confirms, and the customer receives an email payment link. It also clarifies that no payment happens through this tool, which is important for agents to know. This goes beyond what 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?

The description is three sentences: purpose, behavioral flow, and a safety note. It is front-loaded with the primary action and has no wasted words. All content 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 the tool's complexity (12 parameters, no output schema), the description adequately covers the overall behavior: request creation, pending state, operator confirmation, email payment link, and no payment. It also gives a usage guideline. Minor omissions like sandbox mode are handled in the schema, so the description is sufficiently complete.

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 has 100% description coverage, so the schema already documents all parameters. The description mentions 'fixed-price route' and 'no payment' but does not add further meaning to individual parameters beyond what the schema provides. 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 clearly states the action ('Lodge a booking REQUEST'), the resource ('booking'), and the scope ('any fixed-price route — airport or cruise terminal'). It also differentiates from sibling tools like check_availability, get_quote, and get_service_info by focusing on the actual booking action rather than pre-booking steps.

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 provides clear context: use this for fixed-price routes, creates a pending booking, and no payment occurs. It also instructs users to confirm details with the customer first, which is a usage prerequisite. However, it does not explicitly name alternatives or say 'use check_availability first', so it falls short of a 5.

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