tool_find_mistake_fares

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

Since no annotations are provided, the description fully carries the burden. It states 'Read-only. No auth required.' and explains data freshness ('RSS feeds polled at call time, posts typically 1-48 hours old') and limitations ('Does not book or hold fares — prices expire fast, often within hours.').

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?

Well-structured: a concise introductory paragraph stating purpose and behavior, followed by clear usage guidelines and a bulletized parameter list. Front-loaded with key information, no wasted words.

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?

Despite no output schema, the description specifies the return format ('list of deals each with origin, destination, price, sale price, percentage discount, source, and post date'). Covers data freshness, limitations, and usage context. Fully adequate for a simple tool with three optional parameters.

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?

With 0% schema description coverage, the description adds meaning for all three parameters: 'origin: City name to filter deals by departure city... omit to return deals from all origins', 'days_lookback: Include only posts published in the last N days (1-30)', 'max_results: Max deals to return (1-50)'. This provides essential context beyond the bare schema.

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's purpose: 'Fetch recent mistake fares and deal alerts from Secret Flying and Flight Deal RSS feeds.' It uses a specific verb and resource, and distinguishes itself from sibling tools like tool_search_flights and tool_fare_calendar.

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?

Provides explicit guidance: 'Use this when the user wants passive deal discovery without a fixed destination. Use tool_search_flights when the user has a specific route and date in mind. Use tool_fare_calendar for flexible-date price grids on a known route.' This clearly demarcates when to use this tool vs alternatives.

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