add_travel_item

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

The description clearly signals a create/insert action, which is consistent with destructiveHint=false. It adds minimal context beyond the annotation by naming the destination and item categories, but it does not disclose any side effects, duplicate handling, or validation 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 a single front-loaded sentence with no wasted words. It is economical, though it could have used the saved space to add a bit more behavioral or parameter context.

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 tool with 19 parameters, no output schema, and only a sparse annotation, a one-line description is insufficient. It does not tell the agent about the two required fields (though the schema does), item-type-specific requirements, or how the operation integrates with the travel page in the broader workflow.

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 description only reiterates a subset of enum values from the 'type' parameter and does not explain required fields, address formats, or the meaning of source/country_code beyond the schema. With only 53% schema description coverage, the description should compensate but does not.

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 ('Add') with a concrete resource ('travel item') and destination ('Travel page'), and enumerates the covered categories (hotel, flight, train, car, bus). This makes the tool's purpose unambiguous and distinguishes it from sibling tools like update_travel_item and add_poi.

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 phrase 'to the Travel page' gives a clear context for where the item will appear, and the verb 'Add' implies use when creating a new entry. However, it does not explicitly state when to prefer this over update_travel_item, remove_travel_item, or any alternative.

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