Copy File to Device

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

With no annotations, the description must fully disclose behavior. It states the action but omits critical details: whether it overwrites existing files, handles directories recursively, requires specific permissions, or what happens on failure (e.g., file not found, invalid path).

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?

The description is a single, concise sentence that covers the core purpose efficiently. It is front-loaded and easily parsed, but could be slightly more structured (e.g., breaking out prerequisites) without harming conciseness.

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 tool that modifies device storage with no output schema and no annotations, the description lacks completeness. It fails to mention return values (e.g., success indicator), error handling, or behavior for directories vs. files, leaving gaps for an agent.

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 0%, so the description should compensate. It adds context for 'serial' (using serial number) and 'local_file' (from local directory), but 'folder_path_in_device' remains vague. No format hints (absolute/relative), constraints, or mutual dependencies are provided.

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 clearly states the action ('push or copy'), source ('local machine'), destination ('Android device using its serial number'), and specific intent. It effectively distinguishes from sibling tools like pull_file, which does the reverse.

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?

The description implies usage for transferring files to a device but provides no explicit guidance on when to use it versus alternatives like install_app or pull_file. No prerequisites (e.g., device connected, adb available) or exclusions are mentioned.

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