set_gyro_notch1_cutoff

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

No annotations are provided, so the description carries full burden. It discloses that this is a write operation, provides a constraint, and mentions the default value (0) and type (UINT16). However, it does not specify the valid range (0-65535 for UINT16), or what happens if the constraint is violated, or side effects on flight behavior.

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 a single sentence that front-loads the verb and resource, includes the constraint, type, and default. Every part is necessary and no wasted words.

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 setter tool with one parameter and no output schema, the description covers the essential elements: what is set, the constraint, type, and default. However, it could be improved by explicitly stating the units (Hz) and briefly noting the effect on gyro filtering.

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 covers 100% of parameters but only gives type and description 'Value for gyro_notch1_cutoff (UINT16)'. The description adds meaning: 'Bandwidth of gyro notch 1', the constraint relative to gyro_notch1_hz, and the default value. This provides significant added value 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 the action 'Set' and the resource 'gyro_notch1_cutoff' with the meaning 'Bandwidth of gyro notch 1'. It distinguishes this tool from siblings like set_gyro_notch1_hz by specifying cutoff vs. frequency and notch 1 vs. notch 2.

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 explicitly states the constraint 'Must be less than gyro_notch1_hz', which is crucial for correct usage. However, it does not provide explicit guidance on when to use this tool vs. alternatives (e.g., other filter settings) or when not to use it.

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