get_dyn_notch_min_hz

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

No annotations provided. The description indicates it is a read operation ('Get') and includes a type/range hint. It does not detail the function's behavior or return format, but for a simple getter, the background is adequate.

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—two brief sentences plus a bracket note—with no repetition. Every piece of information contributes to understanding the tool.

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 getter with no parameters and no output schema, the description covers purpose, recommended setting, constraints, and a sanity check. It feels complete.

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; schema coverage is 100%. The description adds value by providing a type/range/hint for the value returned, which is beyond the 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 clearly states this tool retrieves the minimum frequency for dynamic notch tracking. It explains what the value represents and provides context on its purpose. Among many get_ siblings, the specific name and description make it unique.

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 gives concrete guidance on setting the value (e.g., 'Set ~25 Hz below the lowest resonance', 'ideally >=150 Hz'), but it does not explicitly state when to use this get tool versus alternatives. The guidance is more about parameter tuning than tool selection.

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