set_gyro_notch1_hz

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

No annotations, so description carries full burden. Describes write operation implicitly, but no details on side effects, persistence, or system impact. Adequate for simple parameter setter.

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?

Single efficient sentence with key info front-loaded. No redundant words. Bracketed type and default add useful detail without clutter.

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 1-param setter with no output schema, description covers purpose, special value, and use case. Lacks explicit unit (Hz) but inferred from name. Reasonably 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?

Adds meaning beyond schema: '0 = disabled', 'centre frequency', default value. Schema only provides type and range; description explains special behavior.

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?

Description clearly states it sets centre frequency of static gyro notch 1, with special value 0 for disable. Distinguishes from dynamic notch and other gyro filters.

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?

Explicitly says 'Use for specific persistent resonances not handled by dynamic notch', providing context for when to use. Lacks explicit when-not-to-use or alternatives, but gives clear indication.

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