tool_find_split_ticket

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

No annotations provided. Description discloses the core operation and risk but fails to mention behavioral traits like read-only nature, whether results are cached or real-time, or if any action is taken beyond searching.

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?

Compact description with a clear purpose sentence, a short warning, and a list of parameters. No redundant information. Could be slightly more structured with parameter formatting, but effective.

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 7 parameters, no output schema, and no annotations, the description covers the tool's purpose and key behavior (savings, risk). Lacks details on return format, preconditions, or side effects. Adequate but not comprehensive.

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?

Args section adds examples and explanations for most parameters (e.g., IATA code format, date format, cabin class options). However, 'adults' and 'currency' are only minimally described, and schema has no descriptions. Modest compensation for missing schema 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?

Clearly states it finds savings by booking two separate tickets through a hub. Differentiates from siblings like tool_find_skiplagged_fares by specifying split-ticket strategy and mentioning expected savings percentage.

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?

Warns about missed-connection risk, guiding agents to surface risks before booking. Does not explicitly state when not to use or compare to alternatives, but the warning provides clear context for prudent usage.

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