get_vbat_duration_for_critical

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

No annotations provided, so description must carry behavioral disclosure. It does not state whether this is read-only, has side effects, or what happens on invocation. The '[UINT8, 0–150, default: 0]' contradicts the empty parameter schema, causing confusion.

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?

Extremely short but relies on an ambiguous cross-reference and includes technical bracket notation that does not belong in a description. Structure is poor.

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 fails to explain what 'vbat_duration_for_critical' means, what the returned value represents, or how it relates to other battery tools. With no output schema and minimal description, the tool is insufficiently documented for an AI agent.

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?

No parameters exist, so baseline is 4. However, the description includes a misleading spec that seems to describe a parameter but no actual parameter is defined, reducing clarity.

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 only says 'Get vbat_duration_for_critical: Same as above but for the critical threshold.' It relies on an unclear 'above' reference and does not clearly state what the tool does. The technical spec in brackets does not clarify the purpose.

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 on when to use this tool versus alternatives like get_vbat_duration_for_warning. The description lacks any usage context or prerequisites.

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