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

Annotations already establish the read-only, non-destructive, open-world profile, so the description earns credit for adding context beyond them: it discloses the default upcoming filter, the returned fields, and an auth requirement (Cotlet API key with access to this app). That auth constraint is the kind of operational detail annotations do not carry.

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 opening sentence and the second sentence overlap heavily, restating route/operator/status twice, and 'Bookings from Your Bookings' is redundant filler. The auth and booking_id guidance are useful but buried at the end rather than 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?

For a two-parameter read-only list with annotations covering the safety profile and no output schema, the description supplies enough: scope, default filter, returned fields, and the API key requirement. It stops short of pagination behavior or how status='all' interacts with ordering, but nothing critical is missing.

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 parameters are already documented in the schema, and the description only echoes the status default of 'upcoming'. It adds no syntax or semantic detail for limit (1-100, default 20) or for how status values map to returned results.

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 clear verb and resource: reads the user's bookings and returns the trips (route, departure, operator, status). The 'bookings from Your Bookings' phrasing is garbled but the intent is recoverable. It distinguishes list-bookings from the sibling point operations by pointing to booking_id usage, though it never names a specific sibling.

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 description implies the primary use case (view trips on your account, upcoming first) and hints that the returned booking_id feeds the other booking tools, but it never states when to prefer this over omio_get_booking or omio_search_trips. No explicit exclusions or prerequisites for invoking it.

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