set_acc_lpf_hz

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

With no annotations, the description carries full burden. It states the tool smooths acc readings for attitude estimation, but does not disclose side effects like need for reboot, persistence, or safety mid-flight. Basic behavioral info is provided, but significant gaps remain.

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?

Two sentences: first defines the tool and its purpose, second provides parameter details. No wasted words, front-loaded with key info. Easily scannable.

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 with one parameter, the description covers basic function, range, and default. However, it lacks usage guidance and behavioral transparency. Given low complexity, it is minimally complete but with notable gaps in those areas.

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 the default value (25) not present in schema, and restates range/type. Purpose of parameter (cutoff frequency) is already clear from tool name and schema. Marginal added value.

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 accelerometer low-pass filter cutoff, explains its effect (smooths acc readings for attitude estimation), and provides range and default. It distinguishes from siblings like set_acc_hardware or set_acc_calibration by focusing on the specific lpf_hz parameter.

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 explicit guidance on when to use this tool versus alternatives. The description implies it adjusts accelerometer smoothing, but does not mention prerequisites, scenarios (e.g., tuning for noisy sensors), or exclusions. Among many set_* siblings, usage context is absent.

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