set_gyro_lpf1_dyn_min_hz

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

With no annotations provided, the description must convey behavioral traits. It mentions the type (UINT16) and default value, but lacks information on persistence (whether changes survive reboot), whether a reboot or arming is required, or any side effects. The schema's huge integer range contradicts the UINT16 claim, but the description does not clarify the actual valid range.

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 with two sentences plus a type/default note. It is front-loaded with the purpose and every sentence serves a clear function with no 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?

For a simple parameter setter with one parameter and no output schema, the description covers the essential purpose, usage tip, and default value. Minor omissions include units and persistence behavior, but overall it 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?

Schema coverage is 100% for the single parameter, so baseline is 3. The description adds a default value and context about the parameter's role as a dynamic cutoff frequency, but does not specify units (likely Hz) or provide additional meaning beyond the schema.

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 it sets the gyro_lpf1_dyn_min_hz parameter, specifies it's the dynamic LPF1 minimum cutoff at low throttle, and distinguishes from static mode by advising to set equal to gyro_lpf1_static_hz. This differentiates it from sibling tools like set_gyro_lpf1_dyn_max_hz and set_gyro_lpf1_static_hz.

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 provides a clear usage tip: set equal to static_hz for static mode, indicating when to use this tool versus static mode. However, it does not explicitly compare with alternatives like set_gyro_lpf1_dyn_max_hz or explain when to adjust the minimum cutoff.

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