custom_route_build

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

No annotations provided, so description carries full burden. It discloses the output (individually-ticketable segments with carrier recommendations) and scenarios handled (mixed carriers, LCCs, Gulf bridge connections, surface sectors). However, it does not mention side effects, auth needs, or statefulness, which would enhance transparency.

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?

Four sentences, each earning its place: core purpose, handling details, credibility statement, usage guidance. No fluff, front-loaded with key info.

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 complexity (4 params, no output schema, no annotations), the description explains the tool's role and niche well. It lacks details on return format or what 'carrier recommendations' entail, but is sufficient for an agent to understand when and why to invoke it.

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 coverage is 100%, so baseline is 3. The description adds context about why you'd use the tool (complex itineraries) but does not elaborate on individual parameters beyond what schema already provides. It helps understand overall purpose but not per-parameter semantics.

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 tool breaks complex multi-city itineraries into individually-ticketable segments with carrier recommendations. It specifies the verb 'break' and resource 'multi-city itinerary', and distinguishes from sibling tools by mentioning handling routes that don't fit alliance fare rules, mixed carriers, etc.

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?

Explicitly says 'Use this for any route with 4+ stops, backtracking, or region combinations that alliance fares can't cover,' giving clear when-to-use guidance. It implies when not to use (simpler routes) but does not name specific alternatives.

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