set_dterm_lpf1_static_hz

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

No annotations are provided, so the description carries the burden. It indicates mutation ('Set') and gives a default value, but does not disclose side effects, persistence, or whether a reboot is needed. This is adequate but minimally transparent.

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 at two sentences, front-loading the purpose, then the condition, then the type/default. Every part is necessary and efficiently presented.

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 the simplicity of a single-parameter setter with full schema coverage, the description provides adequate context for an agent to use it correctly. No output schema exists but is not needed for a setter. Minor gap: no mention of immediate effect or requirement to save/reboot.

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 covers 100% of the parameter with a description, but the description adds the default value (75) and emphasizes that the value is an INT16, which the schema lacks. This extra info improves semantics beyond schema alone.

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' and the resource 'dterm_lpf1_static_hz', explaining it as the 'Static cutoff for D-term LPF1'. This distinguishes it from sibling tools like set_dterm_lpf1_dyn_hz by specifying when it's used.

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 explicitly states the condition for use: 'Used when dterm_lpf1_dyn_min_hz == dterm_lpf1_dyn_max_hz'. This implies that otherwise one should use dynamic variants, though it does not name them explicitly.

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