list_airline_initiated_changes

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

The description directly contradicts the readOnlyHint=true annotation by stating that a fresh call can create a new simulated change in the Duffel sandbox. That is a write-like side effect on session state, so an agent relying on the annotation would be misled about the tool's safety profile.

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?

Three short, purposeful sentences: the first gives the core purpose, and the next two deliver the caching and refresh caveat. There is no filler, and the most important operational warning appears early.

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 2-parameter list tool with an output schema, the description covers purpose, optional-parameter semantics, and cache behavior. It would be more complete with an explicit note that order_id is required and should reference an existing booking, and the annotation contradiction undermines trust in the overall safety model.

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 0%, so the description must compensate. It explicitly explains force_refresh's behavior and when to set it, and 'a booking' ties order_id to the order context. It doesn't state where order_id comes from, but that is largely inferable from the schema and sibling 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?

States a specific action ('List') on a specific resource ('schedule changes the airline made to a booking') and disambiguates the payload ('removed vs added flights'). This clearly distinguishes it from siblings like get_order or accept_airline_change without needing to name them.

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 strong invocation context: it is the read-side view of airline-initiated changes and tells the agent not to set force_refresh unless a re-check is truly needed. It lacks an explicit 'use X instead of Y' comparison with alternatives, but the decision context is otherwise clear.

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