get_calendar_heatmap

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

No annotations are provided, so the description carries full burden. It discloses the scope (~60 days) and mentions it's a single API call, but lacks information on data freshness, pricing sources, or any potential limitations (e.g., incomplete coverage for certain dates).

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, no filler. Front-loaded with core action and key attributes ('~60 days', 'Single API call'). Every word adds utility.

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?

The description does not specify the output format (e.g., list of dates with prices), which is important for an agent to use the result. With no output schema, this gap hinders full understanding. Sibling tools may offer more detail, but for this tool it's incomplete.

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 schema covers 75% of parameters with descriptions. The description adds value by explaining that departureDate is used to retrieve ~60 days of prices around that date, which is not clear from the schema alone. cabinClass default is noted but not elaborated.

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 it 'Get a full calendar of daily flight prices (~60 days)' and distinguishes itself by noting 'Single API call, no scanning,' which differentiates it from sibling tools like search_flights or get_price_history.

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 implies it's for a broad overview ('Shows cheapest dates at a glance'), but it does not explicitly state when to use this tool versus alternatives like search_flights or get_price_history. No exclusions or prerequisites are mentioned.

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