set_gyro_notch2_hz

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

No annotations provided, so description is the sole source. It mentions data type, default, and valid range but does not disclose whether changes take effect immediately, require reboot, or any side effects. Adequate but not comprehensive.

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 concise sentence with essential details (type, default, range). No superfluous words. Ideal length for a simple parameter setter.

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 one-parameter setter, the description covers the parameter meaning, range, and default. Missing guidance on when to use this notch vs others, but overall adequate for the task.

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?

Description adds meaning beyond the input schema: defines the value as centre frequency, explains that 0 disables the notch, and states the default. Schema only says 'Value for gyro_notch2_hz (UINT16)'. Good added context.

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?

Clearly states 'Set' verb and resource 'gyro_notch2_hz', defines it as 'Centre frequency of static gyro notch 2', and specifies valid range (0 = disabled) and type (UINT16). Differentiates from siblings by naming the specific notch.

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?

No explicit guidance on when to use this tool versus alternatives like dynamic notch or other static notches. The description is functional but lacks context for decision-making.

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