update_travel_item

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

Description indicates mutation ('update') and specifies partial update behavior. Annotations show destructiveHint=false, consistent with a non-destructive update. No contradiction; description adds useful context beyond annotations.

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, front-loaded with purpose, and no unnecessary words. Each sentence earns its place.

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?

Adequate for a simple update action, but with 20 parameters and no output schema, the description omits return values, error handling, and field-specific details. Could be more complete.

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 has 20 parameters with only 5% description coverage (only 'travel_entity_id' documented). Description adds no parameter-level meaning beyond schema types and enums, failing to compensate for low coverage.

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?

Description clearly states 'Update a travel item' with the verb 'update' and resource 'travel item'. Distinguishes from sibling tools like 'add_travel_item' and 'remove_travel_item'.

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?

Description provides guidance to 'Provide only the fields you want to change', implying partial update behavior. However, it does not explicitly specify when to use this tool versus other update tools or mention prerequisites.

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