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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true) by disclosing that a fee and price difference are charged, that confirmation happens per call by default and can be toggled off, that the action reaches other people requiring user confirmation, and that a Cotlet API key with app access is required.

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?

Front-loaded with the core action and the fee/confirmation constraints, but the first sentence ('Switch an exchangeable ticket to another departure') and the third ('Switches an exchangeable ticket to the option you pick...') are near-duplicates, costing a little density.

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 two-parameter mutation with no output schema, the description covers the missing pieces an agent needs: financial impact, confirmation semantics, external side effects, and auth requirements. Nothing critical to correct invocation is absent.

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%, so both booking_id and option_id are already documented. The description only restates the option_id provenance already given in the schema, adding no new format or constraint detail; 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?

States a specific verb and resource ('Switch an exchangeable ticket to another departure') and explicitly routes to the sibling tool that supplies the target option ('the option you pick from get_change_options'). An agent can distinguish this from get_change_options, cancel_booking, or book_trip without opening a schema.

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?

Implies the correct workflow (call get_change_options first, then change) and scopes applicability to exchangeable tickets only. It does not spell out when-not to use it (e.g., non-exchangeable tickets) or name a cancellation alternative, so it falls short of full explicit guidance.

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