android_device_info

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description's 'Read' is consistent with a safe, non-mutating operation. The description adds only the scope of what is read and the ambiguous 'optional capability status,' but does not disclose return shape, permission needs, or behavior when capabilities are missing. No contradiction with annotations.

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?

One sentence with no filler, front-loaded with the verb and immediate resource. Every word earns its place by enumerating a distinct information category.

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 zero-parameter, read-only introspection tool the description is close to sufficient, but 'volume' is ambiguous (audio vs storage) and 'optional capability status' is undefined. With no output schema, an agent cannot know the return structure without invoking it, which leaves a real gap.

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 input schema is empty with zero parameters and schema_description_coverage is trivially 100%. There are no parameters for the description to clarify, so the baseline of 4 applies; the description's category list is relevant but not required.

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 uses the specific verb 'Read' and names a clear set of resources: device, Android, battery, storage, network, volume, and capability status. It is broad enough to be distinguished from sibling tools that target single domains like volume or media, though it does not explicitly contrast itself with android_status or android_volume_get.

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 about when to use this tool versus the many sibling tools, nor any exclusions or prerequisites. The intended use case is only implied by the list of categories it reads, so an agent must infer when to prefer it over more specific alternatives.

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