adb_push

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

Without annotations, the description carries the full burden of behavioral disclosure. It lists several pre-flight checks (kernel paths, filesystem type, symlink resolution, storage availability), which is helpful. However, it does not explain what happens on success/failure, whether overwriting occurs, or what the return value represents.

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 sentence that immediately states the main purpose, followed by a list of checks. It is concise and front-loaded, though the list of checks could be formatted more cleanly.

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?

Given a push operation with three parameters and no output schema, the description covers pre-flight behavior but omits details on error handling, post-push state, or confirmation. It is adequate but not fully comprehensive.

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%, meaning all three parameters are described in the schema. The description does not add additional context beyond what the schema provides (e.g., format constraints, special values). Baseline of 3 is appropriate with no extra semantic value.

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 tool's action ('Push a local file to the device filesystem') and includes specific pre-flight checks, making the purpose unmistakable. It distinguishes from similar sibling tools like adb_pull by the direction of transfer.

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 mentions pre-flight checks but does not provide explicit guidance on when to use this tool versus alternatives such as adb_pull or adb_install. The usage context is implied by the action, but no comparative or cautionary information is given.

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