get_upcoming_trips

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

No annotations are provided, so the description carries full burden. It does not disclose whether the tool is read-only, if it has side effects, or any other behavioral traits. The phrase 'Upcoming flight reservations' weakly implies a read operation, but this is not explicit, missing important transparency.

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 sentences: first establishes purpose, second describes the parameter. No wasted words, front-loaded with the core functionality. Ideal structure for a simple tool.

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 simplicity (one optional param, output schema exists), the description is mostly adequate for retrieval. However, it omits what 'upcoming' means (e.g., time window) and any default behavior like sorting. The presence of the output schema helps, but a bit more context would improve completeness.

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 0% description coverage, so the description must compensate. It adds that 'account' is an account name and defaults if omitted, providing basic semantics. However, this is minimal and does not explain format or allowed values beyond the schema type 'string'.

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 'Upcoming flight reservations with record locators' clearly indicates the tool retrieves a list of upcoming flight reservations that include record locators. This distinguishes it from siblings like get_reservation_by_locator (single reservation) and search_change_flights (search/modify). However, it lacks a specific verb like 'list' or 'get', so it's not maximally explicit.

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 only explains the optional account parameter ('Account name (optional, uses default).') but provides no guidance on when to use this tool versus alternatives like get_reservation_by_locator or search_change_flights. There is no mention of prerequisites or typical use cases.

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