set_yaw_lowpass_hz

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

No annotations are provided, so the description carries full burden. It clearly states that the tool sets a low-pass filter on the final yaw PID output, reducing noise. It also discloses the valid range and default. While it does not mention side effects or prerequisites, the behavior is well-explained for a simple setter.

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 three sentences, each serving a distinct purpose: defining the tool, explaining its effect, and providing a usage tip. No redundant or irrelevant information. It is efficiently front-loaded with the most important information.

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 that the tool is a simple one-parameter setter with no output schema and no annotations, the description covers the purpose, effect, range, default, and special behavior. It does not mention persistence or reboot requirements, but for a straightforward parameter setter, this 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%, so baseline is 3. The description adds value by specifying the default value (100) and the special meaning of 0 (disable), which goes beyond the schema's range and description. This helps the agent select appropriate values.

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 explicitly states 'Set yaw_lowpass_hz' with a clear explanation of the filter's location and effect: 'Low-pass filter applied to the final yaw PID output (post-summation). Reduces yaw noise feeding into motors.' It uniquely identifies the resource and action, distinguishing it from sibling 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?

The description provides one usage guideline: 'Set to 0 to disable for maximum yaw responsiveness.' However, it does not specify when to use this tool vs. alternative filter settings or when not to use it. The guidance is minimal and not comprehensive.

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