push

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

No annotations are provided, so the description carries full behavioral burden. It does not disclose overwrite behavior, whether parent directories are created, permission requirements, or error handling for an operation that mutates the device filesystem.

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 single sentence is front-loaded with the verb and contains no filler. Every word contributes to stating the action, making it as concise as possible for the stated purpose.

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 three parameters, 0% schema coverage, no annotations, and the presence of an output schema, the description is too thin. It omits usage guidance, the serial parameter, and behavioral details necessary to invoke the tool confidently.

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 0% and the description only briefly clarifies that local is a host file and remote is a device path. The serial parameter, which selects the target device, is entirely undocumented and the other two parameters receive minimal added meaning.

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 states a specific verb (push) and resource (host file to device path) using the parameter names local and remote. It distinguishes from the opposite sibling 'pull' implicitly by specifying direction, but does not explicitly differentiate from write_file or other file-transfer siblings.

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?

No when-to-use context is given. It does not say when to prefer push over write_file or pull, nor does it mention prerequisites or conditions such as requiring a connected device or root access.

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