get_iterm_relax_cutoff

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

With no annotations, the description fully bears the transparency burden. It discloses that this is a read operation, provides the value's meaning, range, default, and units. No contradictions or omissions.

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?

Description is concise and front-loaded with purpose, then expands with effect, typical ranges, and troubleshooting. Every sentence adds unique value with no redundancy. Appropriate length for the information conveyed.

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?

Despite no output schema, the description fully explains the returned value's meaning, typical values, and adjustment guidance. For a simple getter, this is complete and actionable for an AI 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 tool has no parameters, so the description adds value by explaining the returned value's semantics and range. Per calibration, 0 parameters yields baseline 4, and the description meets that by providing contextual information beyond what schema offers.

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 the tool retrieves the cutoff frequency for the I-term relax HP filter, explains the effect (higher = faster, lower = smoother), and provides typical ranges for different drone types. This distinguishes it from siblings like get_iterm_relax or get_iterm_relax_type.

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?

Description gives implicit usage guidance through tuning ranges and a troubleshooting tip (step down if bounce-back persists). However, it does not explicitly state when to use this tool versus alternatives, nor does it list exclusions.

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