set_vbat_sag_compensation

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

With no annotations provided, the description carries the full burden. It notes the requirement for cell voltage monitoring and a low-voltage warning, but does not disclose whether the change is persistent, if it takes effect immediately, or if it could cause issues mid-flight. The behavioral disclosure is adequate but not thorough.

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 brief (3-4 sentences) and front-loads the core purpose. It efficiently includes the range, default, and a recommended value without extraneous information. Every sentence serves a clear function.

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 single parameter and no output schema, the description covers the parameter's meaning, range, default, and practical usage context (need for cell voltage monitoring). It does not detail what happens after setting (e.g., persistence, immediate effect), but it is fairly complete for a setter in a well-known domain.

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 schema already describes the parameter (integer, 0-150, default 0), so the baseline is 3. The description adds semantic value by explaining that the value represents a percentage target (90% recommended) and its purpose (consistent PID authority). This goes beyond the raw 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 tool's function: compensating for battery voltage sag to maintain consistent PID authority and throttle output. It also provides a recommended target (90%) and the range, effectively distinguishing it from related tools like get_vbat_sag_compensation or set_vbat_sag_lpf_period.

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 includes a recommended value (90%) and prerequisite (cell voltage monitoring) as well as a caution to configure a low-voltage OSD warning. However, it does not explicitly exclude alternative tools or specify when not to use this setting, leaving some room for ambiguity.

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