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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuinely useful context beyond that: fares are the cheapest found in the last 48 hours (data freshness) and the live price lives on the booking page (data currency caveat). This is real behavioral disclosure, not repetition.

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 redundant 'Fare Deals.' lead restates the app name and title, and the middle sentences are promotional ('Cheap flights from any city, to one place or anywhere'). The valuable freshness/caveat sentences are buried at the end rather than front-loaded.

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?

With no output schema, the description should describe what a lookup returns (resolved airport/city codes and names), which it never does. The data-freshness note partially compensates, but an agent cannot predict the return shape.

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 description coverage is 100% and the single 'q' parameter is documented with an example (Lisbon or LIS), so the schema carries the load. The description's 'from any city, to one place or anywhere' hints at scope but adds no format or resolution detail beyond the schema; baseline 3 applies.

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?

States a specific verb+resource pair ('Look up a city or airport code') that an agent can act on. However it does not differentiate itself from the sibling faredeals_find_deals and faredeals_cheapest_dates, and the trailing 'Cheap flights from any city... cheapest days to fly' language describes deal searching rather than a code lookup, muddying the purpose.

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?

No when-to-use guidance and no mention of the sibling tools (find_deals, cheapest_dates) that an agent would need to disambiguate fare-search behavior. The agent must infer this is a resolver/lookup step from the title alone.

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