device_info

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

No annotations exist, so the description carries the behavioral burden. The verb 'Report' implies a read-only query with no destructive side effects, and the listed output fields are a form of behavioral disclosure. However, it does not mention prerequisites (e.g., connected device), what happens if the foreground activity is unavailable, or how serial affects the query.

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?

It is a single front-loaded sentence with zero filler. Every word adds meaning and the size is appropriate for the tool's surface area.

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 likely documents return values, so the four reported fields suffice. The notable gap is the undocumented serial parameter and the absence of any context on how to target a specific device, which makes the description incomplete for a parameterized tool.

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%, so the description needed to compensate, but it never mentions the serial parameter at all. An agent cannot tell what value to pass, whether it selects a device, or why it defaults to null.

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 names a concrete action ('Report') and a specific resource (device info), enumerating four exact data points: screen size, density, Android version, and foreground activity. This is enough to distinguish it from sibling commands like list_devices or screenshot without opening any structured data.

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 explicit when-to-use or when-not-to-use guidance is provided, and the optional serial parameter is never explained. Usage is only implied by the tool's name and output list, rather than stated directly.

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