create_booking_link

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

Annotations already set readOnlyHint=true, destructiveHint=false, but description adds 'Read-only, no account setup, no booking completion, and no reservation side effects' plus 'link may be commission-eligible and is disclosed in output' – valuable context beyond 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 concise sentences: first states core purpose, second provides usage guidelines and behavioral caveats. No redundant information, front-loaded.

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?

Description covers purpose, usage, behavioral traits, and hints at output (commission-eligible link). No output schema exists, but the description provides relevant output context. Slight gap: does not specify if link is returned as a URL string or object, but sufficient for selection.

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% – all parameters have descriptions. Description does not add additional meaning beyond what's already in the schema, so 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?

Description clearly states 'Create an external booking link for an already chosen route' – specific verb+resource. Distinguishes from sibling planning tools by emphasizing the route must already be selected.

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?

Explicit when-to-use ('after route details are known or after compare_airport_routes or plan_flight_route') and when-not-to-use ('use another planning tool first when traveler still needs help choosing'). Also clarifies no booking completion, no reservation side effects.

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