Get Flight Statistics

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

Annotations indicate read-only, nondestructive, and idempotent behavior. The description adds that it includes all flights (past and upcoming) and that distance is provided in both km and miles, which is useful beyond the annotations.

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?

Three concise sentences: first lists what stats are returned, second mentions optional filter, third clarifies scope and output units. 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?

The description covers the output contents and format. With no output schema, this is sufficient for a simple stats tool. It doesn't mention error conditions, but the scope is clear.

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 only parameter (year) has 100% schema description coverage. The description reiterates the optional filter and gives an example, adding minimal value over the 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 it returns aggregate statistics about the user's flight history, listing specific metrics (total flights, distance, unique airports/airlines, top routes, top airlines). This is distinct from sibling tools like flighty_get_flight (single flight) and flighty_list_flights (list of flights).

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 tells users they can optionally filter by year. It doesn't explicitly state when not to use this tool or name alternatives, but the context is clear given sibling tool names.

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