status

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

With no annotations, the description carries the full burden. It implies a read-only informational call via the listed fields, but never states that it is non-mutating, whether it requires an active session/device connection, or what the payload looks like beyond three named items. For a zero-annotation tool that is a meaningful gap.

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 short phrase with no wasted words, but the fragmentary style leaves the action ('reports/returns') unstated and the three listed items are not clearly framed as return values. Brevity here edges toward under-specification rather than efficiency.

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 parameterless diagnostic tool with no output schema, naming the three returned items is minimally sufficient. It does not indicate whether the list is exhaustive (e.g., also device/session state) or the format of values like 'pacing', so an agent cannot fully predict the response.

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 tool takes zero parameters, so there is nothing for the description to disambiguate beyond what the empty schema already shows. Baseline 4 applies.

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 lists the content of the report ('which backends are in use, screen size and pacing'), which distinguishes it from the action siblings like tap or screenshot. However, it is a noun-phrase fragment with no verb ('Returns...' / 'Reports...'), so the operation itself is only implied.

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?

There is no statement of when an agent should call this versus the other diagnostic siblings (observe, app_current, app_list). No prerequisites or exclusion conditions are given, leaving the agent to infer that this is a setup/debugging probe.

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