get_dterm_notch_hz

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

As a simple getter with no annotations, the description discloses the nature ('Static D-term notch centre frequency'), type (UINT16), and default (0). It does not mention side effects or permissions, but none are expected for a read operation. The description adequately conveys safety but could be more explicit about being read-only.

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, using just two sentences with no filler. The purpose is front-loaded, followed by key details (disabled value, usage hint, type/default). Every part adds value.

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 tool's simplicity and lack of output schema, the description covers the return value (centre frequency), type, default, and a usage context. The unit (Hz) is implied by the parameter name. Minor inference needed for exact format, but sufficient for an agent.

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 input schema has zero parameters, so the description adds no parameter info. However, it adds value by stating the return type and default in brackets '[UINT16, default: 0]', which compensates for the lack of an output schema. Schema coverage is 100%.

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 'Get dterm_notch_hz: Static D-term notch centre frequency', specifying the resource and value type. It also notes '0 = disabled' and 'Rarely needed when dynamic notch is active', providing context. The name itself distinguishes from siblings, but there is no explicit differentiation from other get_* 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 when to use it ('Rarely needed when dynamic notch is active'), suggesting preference for dynamic notch when active. However, it does not explicitly state when not to use it or name alternative tools like get_dyn_notch_* for comparison.

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