get_flight_mode

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

With no annotations, the description carries the full burden. It clearly states 'Read-only' and provides an example return value. This discloses the core behavioral trait. However, it does not mention error handling, connection prerequisites, or rate limits, which are minor gaps for a simple 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 two sentences, front-loaded with the purpose, and contains no extraneous information. Every sentence serves a clear function: stating the purpose, noting no arguments, and giving an example output.

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 the tool's simplicity (no parameters, simple output), the description is nearly complete. It covers what the tool does, its input, and its output format. It does not explain possible errors or connection requirements, but for a straightforward getter, this is adequate.

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 tool has zero parameters, and the schema coverage is 100%. The description adds 'Takes no arguments,' which is redundant but confirms the schema. For a zero-parameter tool, baseline is 4, and the description does not detract from it.

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 tool's purpose: 'Report the current flight mode (e.g. HOLD, TAKEOFF, MISSION, RTL).' The verb 'report' and resource 'flight mode' are specific, and the examples distinguish it from the sibling action commands (e.g., arm, takeoff, land).

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 read-only usage by stating 'Takes no arguments. Read-only,' but it does not explicitly say when to use this tool versus alternatives. No guidance on when not to use it or in what contexts (e.g., before taking action). However, the sibling set includes many write commands, so the intent is somewhat clear.

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