file_transfer_root

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose valuable mechanics — Root escalation, /data/local/tmp staging, and the ability to replace files inside private directories (a destructive overwrite). However it omits whether push overwrites existing files, whether the target app must be stopped, and what happens to file ownership/SELinux context when writing into /data/data.

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?

A single compact sentence with the bracketed capability tag front-loaded, followed by the mechanism and the supported path scope. No filler, though the tag is somewhat redundant with the sentence that follows.

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 exists, so return values need not be explained. Still, for a Root-level mutation tool with zero annotations, the definition should say whether push is destructive/overwriting and what the agent must verify beforehand; those gaps keep it at minimum-viable rather than complete.

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 every parameter including action, file_mode, local_path and device_path is already documented in the schema. The description adds only the general framing of 'cross-device pull/push' and no per-parameter detail beyond it, 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 description gives a specific action (pull/push files between host and device) and a specific resource scope (any Root-protected path such as /data/data/ and /data/adb/). The mechanism is also named — routing through /data/local/tmp with Root escalation. It is distinguishable from generic file tools like device_files or app_data_archive, though it never names a sibling explicitly.

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 rather than stated: an agent must infer that this tool is for the root-only paths that ordinary file transfer cannot reach. There is no explicit 'use this instead of X when Y' routing, and no note on preconditions such as requiring Root to be granted first.

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