tool_optimize_budget

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

With no annotations provided, the description fully carries the behavioral disclosure burden. It states 'Read-only. No auth required.', explains the external data source ('Scrapes Google Flights and Hotels live'), warns that 'prices are indicative and may shift', and describes the output structure including ranked date combinations, total cost, per-person breakdown, and booking deeplinks.

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 well-structured with purpose, behavioral notes, usage guidelines, and parameter list in logical order. It is front-loaded with the main action. However, it could be slightly more concise by combining some sentences (e.g., 'Read-only. No auth required.' could be one sentence). Overall, it earns its length.

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 the tool's complexity (8 parameters, no output schema), the description is highly complete. It explains the return value format (ranked date combinations, total cost, per-person breakdown, booking deeplinks), the live nature of data, price limitations, and the effect of flexibility parameters. It also provides usage guidance and sibling alternatives.

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 input schema has 0% description coverage, but the tool's description includes a complete 'Args' section explaining each of the 8 parameters in plain language, adding semantic meaning beyond the schema field names. For example, it clarifies that 'flexible_dates' enables searching around the given dates and 'flexibility_days' defines the window (1-7).

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 begins with a clear, specific verb+resource: 'Find the cheapest flight + hotel combination across flexible date windows.' It explicitly distinguishes from sibling tools by mentioning tool_search_flights and tool_fare_calendar with their respective use cases.

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 description includes an explicit 'Use this when...' statement and directly names alternatives: 'Use tool_search_flights for fixed-date flight-only search. Use tool_fare_calendar for a full month price grid without hotel bundling.' This provides clear guidance on when and when not to use this tool.

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