get_upcoming_trips

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, but the description adds valuable context: it is a read operation, seat assignments are only included when Gondola parsed actual row+letter seats, an API key is required, and the tool returns instructions if no account is connected. This goes well beyond the annotation baseline.

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 description is front-loaded with a clear purpose and then expands into a detailed but justified list of return contents. It is slightly long and has a redundant final 'Returns:' section, but every part contributes useful information about scope, auth, and output behavior.

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 tool has zero parameters and an output schema exists, the description is fully sufficient. It explains what the tool returns, what data fields may appear, what authentication is required, and what happens when the user has no connected account. No essential detail 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?

There are zero parameters, so the baseline of 4 applies; there is no parameter schema gap to compensate for. The description still usefully clarifies what the return payload covers, which is more than enough for a parameterless call.

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 uses a specific verb and resource: 'Get the user's upcoming trips' and enumerates what is included (hotel stays, flights, car rentals). The word 'upcoming' clearly distinguishes it from the sibling get_past_trips, and the content list removes ambiguity about scope.

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 clearly implies this tool is for upcoming travel reservations and notes the prerequisites: a Gondola account and API key. It does not explicitly name alternatives or exclusion conditions, but the contrast with get_past_trips is evident and the fallback behavior when no account is connected is stated.

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