adb_file_move

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

Discloses destructive behavior for system paths (depth ≤1), symlink resolution, and internal copy+delete for cross-filesystem moves. No annotations, so description carries full burden. Could mention permission requirements or error handling, but overall transparent.

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?

Three sentences, front-loaded with purpose. No redundancy. Could combine second and third sentences, but acceptable.

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?

Covers key behaviors but omits return value or output. Given no output schema, description should mention what the tool returns (e.g., success/failure, new path). Also missing device connectivity prerequisites.

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%, so baseline 3. Description adds no extra parameter information beyond what is in the schema. Parameters are clearly described in schema, but description does not enhance understanding.

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?

Clearly states 'Move or rename a file/directory on the device.' Distinguishes from siblings like adb_file_copy (copy) and adb_file_rm (delete). Mentions destructive nature for system paths, reinforcing the move semantics.

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?

Provides implicit guidance (e.g., cross-filesystem moves are slow) and mentions destructive behavior, but lacks explicit when-to-use vs alternatives. No mention of when to prefer adb_file_copy or adb_file_replace.

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