set_airmode_start_throttle_percent

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

Without annotations, the description carries the full burden. It explains that higher values cause motors to idle before airmode engages, which is useful behavioral insight. It also provides type, range, and default, adding transparency.

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 very concise with three sentences: purpose, behavioral effect, and constraints/range. No redundant information; every sentence earns its place.

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 a single-parameter setter with no output schema, the description covers purpose, behavioral effect, and constraints. It could mention prerequisites or side effects, but for a simple parameter write, it is sufficiently complete.

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%, but the description adds value by explaining the parameter's role (throttle threshold for airmode) and the effect of higher values. The default value is also stated, which is not in the schema description.

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 sets the throttle percentage at which airmode activates. It specifies the verb 'Set' and resource 'airmode_start_throttle_percent', and the function is distinct from sibling get/set tools for other parameters.

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 for configuring airmode behavior but does not provide explicit when-to-use or when-not-to-use guidance. It lacks comparison with sibling tools like other set_ functions, so the agent must infer usage context.

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