set_d_max_advance

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

With no annotations, the description carries full burden. It discloses that the setting 'can cause premature D oscillation' and is 'rarely beneficial.' It explains the mechanism ('uses feedforward signal'). This is adequate for a simple parameter, though more detail on consequences could be added.

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 three sentences plus a technical bracket, all adding value: purpose, tuning advice, exploration advice, and spec. No wasted words, well-structured, and front-loaded.

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 single-parameter setter with no output schema, the description covers purpose, usage, risks, and default thoroughly. It is complete for the tool's complexity.

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% (parameter description in schema). The tool description adds meaning beyond the schema: it explains the feedforward signal timing and provides the default value (20). This adds significant context for parameter selection.

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 tool's purpose: 'Allows D boost to start before the gyro rate peaks, using feedforward signal.' It uses specific verb+resource and distinguishes this parameter from other D-related settings like set_d_max_gain or set_d_max_pitch.

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 gives explicit usage guidance: 'Set to 0 during baseline tuning' and 'Only explore once the baseline is stable.' It warns that it's 'rarely beneficial and can cause premature D oscillation.' No alternative tool is named, but the context is clear enough.

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