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

No annotations are provided, so the description carries the full burden, and it does state 'Read only' as an explicit safety signal. It also discloses that the wallet param is never used to send anything, which is valuable behavioral context. It omits any mention of failure modes or whether status is real-time vs. cached.

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?

It is dense and front-loaded with the domain framing first, then the return contents, then the action routing, then the safety note. The middle sentence is a long run-on enumeration, but each clause (window end, applicant count, winning application once drawn, outcomes) carries distinct information rather than filler.

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?

There is no output schema, so the description must explain return values, and it does so thoroughly: run lifecycle states (accepting applications, seat lottery, awaiting drand draw, finished with won/lost/expired/void) plus wallet-specific fields. Combined with a fully documented 2-param schema, an agent has what it needs to call this 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?

Schema coverage is 100%, so baseline is 3; the description adds meaning by explaining what the wallet parameter actually unlocks (flight status, cooldown, claimable winnings) beyond the schema's 'read balance and allowance and simulate'. The n parameter is only implied by 'latest runs' and relies on the schema for its 1–30 range.

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 establishes the resource (AirRun: helicopter and private-jet runs) and effectively states that it reads current run state, enumerating the categories of runs returned. It doesn't lead with a clean verb like 'List' or 'Get', but an agent can still tell it's a read of air-run status. It distinguishes itself from prepare_air_run, the only closely related sibling.

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?

'Take a run with prepare_air_run' explicitly routes the agent to the alternative action tool, and 'Pass wallet for its flight status, cooldown and claimable winnings' gives concrete usage context for the optional param. It stops short of stating when not to call it or any prerequisites (e.g. does it need wallet login first?).

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