set_dyn_idle_max_increase

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

No annotations are present. The description only states what the parameter is and its range, but it does not disclose behavioral traits like whether a reboot is needed, effect on flight performance, or safety considerations.

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 parameter's purpose, range, and default. Every element 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?

For a simple setter of a single parameter, the description adequately explains the parameter's meaning and allowed values. Missing behavioral context is minor given the tool's simplicity.

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% with a description for the parameter. The tool description adds meaningful context by explaining the unit (motor units) and role (above static idle), going beyond the schema's generic 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 verb 'Set' and the resource 'dyn_idle_max_increase', explaining it as the maximum throttle increase above static idle. While it distinguishes this parameter from others, it does not differentiate it from many similar set_ tools.

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 guidance on when to use this tool versus alternatives (e.g., set_dyn_idle_p_gain). No prerequisites or typical scenarios are provided.

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