get_aircraft_state

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

No annotations are provided, so the description carries full burden. It lists what is included but does not disclose behavioral traits such as whether it is real-time, cached, or has side effects. Minimal but adequate for a read-only tool.

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 that efficiently conveys the tool's purpose and contents. Every word earns its place; no fluff.

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?

Given zero parameters, an existing output schema, and the simple nature of the tool, the description is complete. It sufficiently informs the agent about what the tool returns.

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?

With 0 parameters and 100% schema coverage, the baseline is high. The description adds value by enumerating the output categories (position, attitude, speeds, etc.), which is helpful given the absence of an explicit output schema display.

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 it's a 'Bundled snapshot' and lists the specific categories (position, attitude, speeds, etc.), making the verb ('get') and resource ('aircraft state') unambiguous. It distinguishes itself from siblings like get_simvar by implying a bulk return of multiple state variables.

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 use when a combined snapshot of aircraft state is needed, but does not explicitly exclude alternatives like get_simvars (which also returns multiple) or detail when not to use it. However, the context is clear given the bundled nature.

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