node_transfer

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

No annotations are supplied, so the description carries the full behavioral burden. It does add real value by disclosing SHA-256 verification and block delta sync, but those are already partially echoed by the use_delta schema field, and it says nothing about overwrite behavior, atomicity, what happens on hash mismatch, or failure/return semantics for a write operation.

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?

A single front-loaded sentence with no filler: verb first, then endpoints, then verification guarantees. The embedded list of node identifiers is slightly dense but every clause earns its place.

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 seven-parameter mutation tool with no annotations and no output schema, the description covers intent and verification but leaves behavioral gaps an agent would want, notably overwrite/merge behavior on the destination and what the caller receives on success or hash failure. Rich schema coverage compensates for the parameter side, but the mutation semantics remain thin.

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 all seven parameters, including the direction enum and the tx_id idempotency note, are already documented in the schema. The description adds no syntax, format, or constraint detail beyond what the schema provides, making baseline 3 appropriate.

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 names a specific verb pair (push/pull) and resource (a file) plus the exact endpoint universe ('@appliance', '@bastion', TargetNode), so an agent knows this is a file-transfer tool rather than a read/patch/exec tool. It stops short of explicitly differentiating itself from siblings like node_sync or node_read_file, but the verb+resource is unambiguous.

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?

There is no when-to-use guidance: nothing says when to choose node_transfer over node_sync, node_read_file, or node_patch_file, and no prerequisites or exclusions are stated. The agent must infer usage purely from the verb and the node list.

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