phones

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so safety is fully covered without the description's help. The description adds only the "already set up" scoping nuance and says nothing about whether it queries adb, what happens with zero devices, or how results are ordered or truncated.

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 fragment with no wasted words, so brevity is not the problem. But it is under-specified rather than concise – a sentence-fragment noun phrase that leaves the reader to reconstruct the action being performed.

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-optional-parameter read tool with no output schema, the description should at least convey that the result is a list of attached devices and what identifying fields it contains. As written, an agent cannot tell what the return looks like or what an empty result signifies.

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 optional `device` parameter is fully documented in the schema as an adb serial needed only when several phones are connected. The description adds no further meaning beyond that, so the baseline of 3 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 fragment "Phones already set up on this computer" implies enumerating currently connected/configured devices rather than discovering new ones, which does distinguish it somewhat from siblings like scan or doctor. However, it is a noun phrase with no verb at all – an agent must infer that the tool returns a list rather than, say, opens a phone manager UI.

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 when-to-use guidance and no alternative named. The phrase "already set up" faintly hints this is for known devices as opposed to an unconfigured one, but no sibling (scan, doctor, playbook) is referenced to make that contrast actionable.

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