save_itinerary

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not state whether saving is idempotent, whether it overwrites existing trips, what authentication or permissions are required, or what the response format looks like. The single sentence provides minimal transparency beyond the action itself.

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 a single concise sentence with no redundant words, and the key details ('Save', 'itinerary', 'user's trips') appear early. However, its brevity borders on under-specification, omitting important behavioral details that could be included without significant expansion.

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 there is no output schema, no annotations, and the tool performs a write operation, the description is incomplete. An agent lacks information about success/failure indicators, side effects, or how this relates to existing user trips. The tool would benefit from additional context about saving behavior and integration with other itinerary management tools.

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 (custom_title and itinerary_id) are already documented in the input schema. The description itself adds no extra meaning or context for the parameters, leaving them fully defined by the schema. Baseline 3 applies.

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 states a clear action ('Save') and resource ('an itinerary to user's trips'), which communicates the core purpose. However, it does not explicitly differentiate from sibling tools like create_itinerary or modify_itinerary, relying on the verb 'save' to imply a distinct operation.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention prerequisites, conditions, or which scenarios call for saving an itinerary versus creating or modifying one.

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