tool_save_trip

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

No annotations are provided, so the description carries the burden. It discloses the return value (trip_id + checklist) and implies persistence by saying 'persists across sessions.' However, it does not explicitly state that the tool creates a new trip (vs. updating an existing one) or any authentication/permission requirements.

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 efficiently written: a short high-level statement, a one-sentence usage hint, then a structured list of parameters. No redundant or irrelevant information; every sentence adds value.

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 an 8-parameter tool with no output schema or annotations, the description covers the key aspects: purpose, when to use, what it returns, and parameter formats. Missing details like the exact contents of the booking checklist or constraints on date ordering are minor gaps.

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%, but the description's Args section adds meaning for all 8 parameters (e.g., 'destination: City or country', 'depart_date: YYYY-MM-DD', 'origin: Home airport IATA'). This compensates well for the lack of schema descriptions, though some parameter explanations could be more precise (e.g., purpose enum).

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 clearly states the verb ('Save'), the resource ('a trip'), and the outcome ('Returns a trip_id + 8-item booking checklist'). It distinguishes from siblings like tool_delete_trip and tool_update_trip by focusing on initial saving of a planned trip.

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?

Explicit usage context: 'Use when a traveler commits to a destination so progress persists across sessions.' This tells the agent when to invoke the tool, though it does not explicitly mention when not to use it or list alternatives among the many sibling tools.

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