set_anti_gravity_cutoff_hz

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

No annotations provided, so description carries full burden. States it's a set operation (mutation) but doesn't disclose side effects, permissions, or state changes. For a simple parameter setter, this is adequate but not exceptional.

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?

Two sentences plus a compact type/range/default note. All information is front-loaded and every part adds value. No redundancy or unnecessary detail.

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 single-parameter setter with no output schema, the description is sufficiently complete. It explains the purpose, parameter semantics, and tuning guidance. No obvious gaps given the tool's simplicity.

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?

Schema coverage is 100% for the single parameter, but description adds meaningful context: explains what the parameter controls (LPF cutoff for throttle derivative) and its effect on response time. Also provides range and default in text.

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 a LPF cutoff for throttle derivative used by anti-gravity, with specific verb 'Set' and resource 'anti_gravity_cutoff_hz'. It distinguishes from sibling get_ and set_ tools for other anti-gravity parameters by specifying the exact parameter being set.

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?

Provides tuning guidance: adjust for very large or small builds, with direction of effect (larger = faster response). Lacks explicit when-not-to-use or alternatives, but the context of adjustment is clear given the single parameter.

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