set_vbat_duration_for_warning

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

No annotations provided, so the description carries full burden. It explains the parameter's role and range, but does not disclose potential behavioral aspects such as persistence, interaction with other settings, or any side effects. The description is adequate but not exhaustive.

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 extremely concise, consisting of two short sentences plus an inline specification. It is front-loaded with the tool's purpose and includes all critical information with no wasted words.

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 simplicity of the tool (single parameter, no output schema), the description is nearly complete. It explains the parameter's function within the warning alarm context. However, it does not mention related settings like the warning threshold itself, but this is acceptable for a focused setter.

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% (the 'value' parameter is described). The description adds context by explaining the unit (tenths-of-seconds), the purpose (prevent false alarms), and the range/default, providing semantic value beyond the 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 that this tool sets the duration for which voltage must remain below the warning threshold before the alarm fires, distinguishing it from the sibling 'set_vbat_duration_for_critical' by specifying 'warning alarm'. The verb 'Set' and the resource 'vbat_duration_for_warning' are explicit.

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 implies when to use the tool by noting it 'Prevents brief-spike false alarms', but it does not explicitly compare with alternatives like 'set_vbat_duration_for_critical' or 'set_use_vbat_alerts'. No explicit 'use when' or 'when not to use' statements.

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