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

With no annotations provided, the description carries the full burden. 'Get' implies a read-only operation, and the listed outputs (level, charging state, temperature) hint at behavior, but the description does not disclose edge cases such as device availability, units of temperature, or whether the device must be powered on. It does not contradict anything, but it is minimal.

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 a single front-loaded sentence with no filler. It names the action, target, platform, and core output fields in one compact statement.

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?

For a simple one-parameter read-only device query, the description is mostly complete: it identifies the target, platform, parameter, and return information. It would be more complete if it specified units or exact output shape, but the lack of an output schema makes its current level adequate.

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%, and the single parameter udid already has a clear description ('Device serial number (UDID)'). The tool description adds no extra parameter-level meaning, so it does not exceed the schema baseline.

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 states a specific verb ('Get'), a specific resource ('battery status'), and a platform scope ('Android device'), then enumerates the returned data: level, charging state, temperature. It clearly distinguishes this from iOS sibling tools like ios_battery by naming the Android platform.

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 makes clear this tool is for Android devices, which effectively routes the agent away from ios_battery and other non-device tools. It does not explicitly name an alternative or state when not to use it, but the platform constraint is clear and sufficient for basic selection.

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