get_airmode_start_throttle_percent

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

No annotations are provided, so the description must cover behavioral aspects. It discloses the UINT8 type, range (0–100), and default (25), which is helpful. However, it does not mention any side effects, idempotency, or whether the tool requires a connected flight controller. The description provides basic transparency but lacks depth.

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 extremely concise, consisting of two informative sentences plus a technical spec. Every part adds value: the title, the definition, the behavioral note, and the type/range/default. No wasted words.

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 parameter getter tool with no input parameters and no output schema, the description provides all essential information: what is retrieved, its meaning, and its valid range. The agent can use this tool confidently without additional context.

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 zero parameters, so schema coverage is trivially 100%. The description does not need to explain parameters. Baseline 3 applies, and no additional value is provided.

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 retrieves the throttle percentage for airmode activation. It uses the verb 'Get' and specifies the resource 'airmode_start_throttle_percent'. The behavioral note about motors idling at higher values adds clarity. The existence of a sibling setter tool provides clear differentiation.

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?

No explicit when-to-use or when-not-to-use guidance is provided. The pairing with 'set_airmode_start_throttle_percent' is implicit but not mentioned. For a simple getter, the usage is straightforward, but the description does not confirm or exclude specific scenarios.

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