push_adb_file

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the risk profile is known; the description still adds real value by explaining the overwrite refusal default and the post-transfer digest comparison against the device's sha256sum. It stops short of saying what happens when the digest mismatches (abort, cleanup, partial file) or what errors surface, which is the key remaining behavioral question for a mutation tool.

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?

Two sentences, no waste, with the core action front-loaded and the safety/verification traits following. Every clause carries information an agent would otherwise have to guess.

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 destructive five-parameter tool with no output schema, the description covers the essential safety model (overwrite gating, digest verification) that the schema does not. It leaves the return shape unstated, which matters somewhat since there is no output schema to describe whether the digest result is reported back to the caller.

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 overwrite, local_path, device_path and analysis_project_id is already documented in the schema. The description's mentions of overwrite and absolute paths restate schema content rather than adding new semantics; baseline 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?

States a specific verb+resource+scope: 'Push one local file to an absolute device path', which cleanly distinguishes it from the reverse-direction sibling pull_adb_file. The claim that it is 'the only device-mutating ADB tool' is questionable given siblings like install_adb_package, uninstall_adb_package and stop_adb_app, which weakens an otherwise precise statement of purpose.

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?

Gives a concrete usage condition and a when-not: existing device files are refused unless overwrite is explicitly requested, which tells the agent exactly when the call will fail and how to proceed. It does not explicitly name pull_adb_file as the alternative for the opposite direction, leaving that inference to the agent.

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