get_battery

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the underlying source ('from dumpsys battery') and the read-only nature is implied by 'Return', but it says nothing about which device is targeted, behavior with multiple connected devices, or failure modes.

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?

A single compact sentence that front-loads the verb and enumerates the payload; every word earns its place.

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?

An output schema exists, so return values need not be explained, and the read-only nature is inferable. However, with zero annotation coverage and an undocumented 'serial' parameter, the description leaves device targeting and multi-device behavior unspecified.

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 0% and the sole parameter 'serial' is undocumented in both schema and description. The description never mentions device selection, so an agent gets no help in understanding what 'serial' does or how to pick a device.

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?

Specific verb ('Return') plus resource ('battery') and it enumerates the returned fields (level/status/health/temperature), which no sibling tool covers. It does not explicitly differentiate itself from siblings like get_device_properties or dumpsys, but the battery focus is unambiguous.

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?

Usage is only implied by the tool name; the description gives no explicit when-to-use, prerequisites, or alternatives (e.g., use dumpsys for a full battery dump). Adequate but with a clear gap.

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