set_altitude_d_lpf

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

No annotations are provided, and the description only defines the parameter. It lacks any disclosure of behavioral traits such as persistence, side effects, or whether a reboot is required. This is a significant gap given the absence of annotations.

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 sentence plus a bracket, front-loading the purpose and key details. Every word serves a purpose, and there is no unnecessary 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?

The tool is simple, but without annotations, the description should cover basic behavioral context (e.g., immediate effect, reboot needed). It does not, leaving the agent partially uninformed.

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%, but the description adds value by explaining the parameter's function (low-pass filter cutoff for vertical speed), units (Hz×10), and default value (100), which are not in the schema description.

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 verb 'Set', the resource 'altitude_d_lpf', and specifies that it is a low-pass filter cutoff for altitude derivative (vertical speed). It includes units (Hz×10), range, and default, distinguishing it from siblings like set_altitude_lpf.

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 vertical speed filtering via 'altitude derivative', differentiating from set_altitude_lpf. However, it does not explicitly state when to use or when not to use this tool, nor does it mention alternatives.

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