set_altitude_lpf

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

No annotations are present, so the description bears full responsibility. It discloses the tool is a setter for a filter parameter and describes the trade-off, but does not mention side effects, persistence, or if a reboot is required.

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 efficient sentence with the range and default in brackets. No wasted words; all information is front-loaded and essential.

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 input and no output schema, the description covers the core purpose, effect, range, and default. It could mention whether changes take effect immediately or after reboot, but overall it is sufficient.

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?

The schema already fully describes the parameter (type, range), but the description adds the default value (300) and the unit (Hz×10), which are absent from the schema. This provides meaningful extra context.

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 a low-pass filter cutoff for altitude estimate, specifying the unit (Hz×10) and effect (smoother but laggier). It uniquely identifies the resource ('altitude_lpf') and distinguishes it from many sibling 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?

The description implies usage for adjusting altitude filter smoothness but does not explicitly state when to use this tool versus alternatives (e.g., other filter settings). No prerequisites or when-not-to-use guidance is provided.

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