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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds real value beyond that: it discloses the transport ('device file-sync protocol, no shell roundtrip') and the symlink resolution rule ('one level'), which are non-obvious behaviors an agent should know.

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?

Four tight sentences, front-loaded with the core action, then transport, return shape, and path hints. Every sentence carries distinct information and there is no filler.

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?

With no output schema, the description helpfully inlines the return shape ({ ok, remotePath, count, entries }). It covers transport, path conventions, and symlink handling. The only gap is that recursion behavior (does it list subdirectory contents or only immediate children?) is not explicitly stated.

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 100%, so both parameters are already documented with examples (including '/sdcard/Download' for remotePath). The description's list of common roots (/sdcard/, /sdcard/Download, /sdcard/DCIM) marginally enriches remotePath but largely repeats the schema's example. Baseline 3 is appropriate.

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?

States a specific verb ('List') and resource ('files and directories at a path on the device'), which is clear and unambiguous. However, it does not distinguish itself from close siblings like device_file_find or device_file_stat, which an agent could easily confuse for a directory listing.

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?

Usage is implied through the 'common roots' examples, which hint at typical Android storage paths, but there is no explicit guidance on when to use this versus device_file_find (search) or device_file_stat (single-entry metadata). The agent must infer the distinction from tool names.

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