get_dterm_lpf1_dyn_expo

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

No annotations provided, but the description discloses the return type and range (UINT8, 0–10, default 5), which is important behavioral context for a getter tool.

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?

Three sentences with no wasted words. Front-loaded with purpose and includes tuning advice and type info. Appropriate length for a simple getter.

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 parameterless getter with no output schema, the description provides sufficient context: what the value represents, tuning guidance, and data type/range. Could be more explicit about the return value, but 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?

No parameters exist, so schema coverage is 100% trivial. The description adds value by specifying the return value's data type, range, and default, compensating for the lack of output schema.

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 states it gets 'dterm_lpf1_dyn_expo' and explains it is the 'Expo curve for dynamic D-term LPF1 vs throttle.' This clarifies the purpose, though it does not explicitly differentiate from sibling getters for similar parameters.

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?

Provides a tuning guideline ('Push as high as possible without mid-throttle oscillations') but does not explain when to use this getter over alternatives like the setter or other dterm parameters.

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