set_vbat_duration_for_critical

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

With no annotations, the description must disclose behavioral traits. It only repeats schema constraints (UINT8, 0–150) and mentions a default (0). It does not describe side effects, persistence, or whether a restart is required, leaving important behavioral information missing.

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 very short, but the phrase 'Same as above' indicates it was likely copied from a list without adaptation. This reduces clarity and suggests poor structure, as the description should be self-contained.

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?

The description does not explain the system-level role of vbat_duration_for_critical (e.g., battery alert duration). The schema covers all parameters, but the agent lacks understanding of the parameter's purpose within the broader battery monitoring context.

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 description adds the default value '0', which is not present in the input schema, providing useful context beyond the schema's min/max/description. This extra information helps the agent understand the expected initial state.

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 verb 'Set' clearly indicates a write operation, and the resource 'vbat_duration_for_critical' names the parameter. However, the phrase 'Same as above' is ambiguous because there is no preceding description in this context, making the purpose less clear than it could be.

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?

No guidance is given on when to use this tool versus alternatives like set_vbat_duration_for_warning. The agent receives no context about how the critical threshold differs from the warning threshold or when each is appropriate.

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