adb_battery_drain

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

No annotations are provided, so the description must fully disclose behavior. It mentions taking initial and final readings and calculations but omits whether it modifies system state, requires extra permissions (except per-package via schema), or how it affects battery stats. A mutating tool like this should state if battery stats are reset or if the device remains awake.

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?

Two sentences, front-loaded with the core action and outputs. Every sentence is relevant and no redundancy.

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 no output schema or annotations, the description should be more thorough. It does not specify output format, duration of measurement process, required device state (e.g., screen on), error conditions, or limitations (e.g., needing steady battery). This leaves gaps for the 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?

Schema description coverage is 100% (all three parameters have descriptions). The tool description adds only a high-level context ('over a specified duration') but does not elaborate on parameter details beyond what the schema provides. Baseline 3 is appropriate.

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 purpose ('Measure battery drain rate over a specified duration') and lists specific outputs (mA draw, mW, percentage per hour). It distinguishes from sibling tool 'adb_battery' by emphasizing rate calculation over a duration.

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?

Provides a typical use case ('power impact of specific operations') but lacks explicit guidance on when or when not to use, or alternatives. No exclusion criteria are mentioned.

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