list_my_flights

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

No annotations provided, so description carries transparency burden. It discloses filtering options and that output includes geo coordinates, but does not mention ordering beyond 'newest first' in limit param, pagination, error handling, or authentication needs.

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?

Description is front-loaded with purpose, then parameter details. Slightly verbose with 'Args:' label, but overall efficient and clear. Could be trimmed but still good.

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?

Covers input parameters well. Mentions output includes geo-coordinates for departure/arrival. With output schema present, not fully describing output is acceptable. Slight gap: doesn't explicitly state output is a list of flight legs.

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 coverage is 0%, so description compensates fully. Each of the 5 parameters (year, after, before, upcoming_only, limit) is explained with clear semantics and usage context, e.g., 'after: Only flights departing on/after this ISO date (YYYY-MM-DD).'

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?

Description clearly states it lists the user's own flights as geo-ready legs with departure/arrival airports and coordinates. Distinguishes from siblings 'get_flight' and 'flight_stats' by focusing on list of flights with geo data.

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?

Description implies use when needing a list of own flights with geo coordinates, but does not explicitly state when to use this versus siblings 'get_flight' or 'flight_stats'. No when-not or alternative guidance provided.

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