set_d_max_gain

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

With no annotations, the description carries the full burden. It explains the behavioral effect (aggressiveness of D rise), the data type (UINT8), valid range (0–100), and default value (37). This provides good transparency, though it omits whether changes take effect immediately or require reboot.

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 two sentences plus a compact bracket notation for type/range/default. It is front-loaded with the core function and wastes no words. Every sentence serves a purpose.

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?

Given the tool's simplicity (one parameter, no output schema) and the presence of type/range/default/tuning advice, the description covers the essential aspects. A minor gap is the lack of information about effect timing (immediate vs. restart), but it is still fairly complete for its 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?

The only parameter 'value' has 100% schema coverage with a basic description. The tool description adds a default value (37) and tuning advice ('reduce if propwash'), which enriches the schema and helps the agent choose appropriate values. This goes beyond the schema's static range declaration.

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 that the tool 'Controls how aggressively D rises from base D toward d_max on sharp moves.' It uses a specific verb-resource combination and distinguishes itself from numerous sibling set_* tools by explaining its precise role in D boost behavior.

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?

Explicit guidance is given: 'Default is suitable; reduce if D boost causes propwash on move initiation.' This tells the agent when to adjust the parameter and in which direction. No alternatives are mentioned, but the advice is practical and context-aware.

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