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

No annotations are supplied, so the description carries the full burden and provides almost nothing: no indication of return format, whether system apps are included, ordering, pagination, or whether the device must be online/parked. The single clause about user-installed scope is the only behavioral hint.

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 short and front-loaded, so nothing is wasted, but it is a sentence fragment rather than a structured statement of purpose and behavior. Brevity here reflects under-specification more than disciplined editing.

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 single-parameter read tool this could be adequate, but with no annotations and no output schema the description is the only source of behavioral information and says nothing about what the call returns. An agent cannot tell whether it gets package names, labels, or versions.

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?

With one parameter at 100% schema description coverage ('Phone id, ph_…'), the schema already does the work; the description's phrase 'on this phone' merely echoes the phone_id concept without adding format or constraints. Baseline 3 applies when the schema fully documents the parameter.

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 'Apps the user installed on this phone' identifies the resource (installed apps) and implies a listing, but never states the verb and reads close to a restatement of the name list_apps. It does add the scope 'user-installed' which hints at excluding system apps, but does not distinguish this from siblings like install_app or list_phones in any explicit way.

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, no mention of prerequisites (e.g., the phone must exist or be running), and no reference to alternatives such as install_app/uninstall_app or list_phones. The agent must infer the call context entirely from the tool name.

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