get_airport_arrivals

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

With no annotations provided, the description does not disclose behavioral traits such as rate limits, authentication requirements, or data freshness. It only states the basic purpose, leaving agents unaware of important operational constraints.

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 short and front-loaded with the tool's purpose. Parameter explanations are clear and contained within a structured docstring format. No superfluous information is present.

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 two-parameter tool without output schema, the description adequately covers parameter semantics. However, it omits details about the return format, pagination, or error handling, which could be useful for completeness.

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?

Despite 0% schema description coverage, the description provides concrete examples for airport_icao (e.g., EDDF, KJFK, EDDM) and explains the hours parameter with default and maximum values. This adds significant clarity beyond the bare 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 'Letzte Ankünfte an einem Flughafen abrufen (OpenSky)' meaning 'Retrieve latest arrivals at an airport'. It specifies the resource (arrivals) and action (retrieve), and it effectively distinguishes from siblings like get_airport_departures.

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 airport arrivals, but lacks explicit guidance on when to use this tool versus alternatives like get_airport_departures. No exclusions or context are provided, relying on sibling names for differentiation.

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