set_horizon_delay_ms

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

No annotations are provided, so the description carries the full burden. It discloses the effect on flight behavior (delays return-to-level) and specifies valid range and default, but does not mention whether changes require reboot, persist, or if any state dependencies exist. Adequate for a simple parameter setter but could be more transparent.

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 concise at three sentences: action + explanation + technical details. It front-loads the purpose and provides all necessary information without redundancy.

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 is a simple parameter setter with one parameter and no output schema, the description is reasonably complete. It covers purpose, effect, and valid range. Lacks mention of any runtime constraints (e.g., if settable while armed), but overall sufficient for an agent.

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%, setting baseline at 3. The description adds significant value beyond the schema by explaining the behavioral impact (more acro-like feel) and the range/default values, whereas the schema only provides minimal type/range info.

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 action (set horizon_delay_ms), explains the parameter's function (time before horizon mode re-applies leveling after sticks return to center), and its effect (more acro-like feel). It distinguishes itself from sibling set_* tools by naming the specific parameter and its role in horizon mode.

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 usage for adjusting horizon mode behavior but provides no explicit guidance on when to use this tool versus alternatives (e.g., set_horizon_ignore_sticks, get_horizon_delay_ms). No when-not or prerequisite information is given.

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