aircraft_arrivals

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Get recent arrivals' but fails to define 'recent', specify the default time range, clarify if results are real-time, or describe what happens when no arrivals are found. This is minimal for a read operation.

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 a single sentence, front-loaded with the verb and resource, and contains no superfluous words. Every part earns its place with high efficiency.

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 simple tool with 3 parameters and no output schema, the description is minimally complete. However, it lacks explanation of the term 'recent', default time ranges, and the existence of optional begin/end parameters, which would help an agent understand tool capabilities fully.

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 has 100% coverage for parameter descriptions, so the baseline is 3. The description adds no additional meaning beyond mentioning 'ICAO code' for the airport parameter, which matches the schema. No extra context is provided for begin/end parameters.

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 the verb 'Get', the resource 'recent arrivals', and the key parameter 'by ICAO code'. It is distinct from sibling tools like aircraft_departures (departures vs arrivals) and aircraft_flights (which may be both directions).

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 usage for retrieving arrivals at a specific airport but does not provide explicit context on when to use this tool vs alternatives (e.g., aircraft_departures for departures) or any exclusion criteria. It does not mention the time range defaults or notes on how to adjust it.

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