airline_info

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

With no annotations provided, the description carries the behavioral transparency burden. It discloses the read-only lookup nature, the input format, and the exact output fields. It does not discuss error handling for invalid codes, but for a simple lookup tool this is a minor gap.

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 description is concise, front-loads the primary lookup action, and uses examples economically. Every sentence adds value, and the line breaks make it scannable.

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?

For a single-parameter lookup tool with no output schema, the description is complete: it explains the input, the expected output fields, and gives concrete examples. Nothing essential is missing for an agent to call the tool correctly.

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 input schema merely says 'Code' with no description, so parameter semantics rely entirely on the tool description. The description clearly defines code as an ICAO code, explains it is the callsign prefix, and provides real-world examples. This fully compensates for the 0% schema description coverage.

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 uses a specific verb and resource: 'Look up an airline by its ICAO code' and clearly states what will be returned (name, IATA code, country, callsign). The examples (JBU, BAW, UAE) make the tool's purpose unambiguous and distinguish it from aircraft-centric siblings like identify_aircraft or search_aircraft.

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 clearly implies when to use the tool: when you have an ICAO airline code and need airline metadata. It does not explicitly name alternative tools or state when not to use it, but the examples and the focus on airline codes give sufficient operational context.

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