transfer_file

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

No annotations are provided, so the description carries the full disclosure burden. It does reveal the transport ('via SCP'), which is useful, but says nothing about authentication requirements, overwrite behavior on existing remote files, size/timeout limits, or what happens on partial failure — all material for a write-capable 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; the core action and protocol come first. It is efficient, though it is arguably too short given the tool's complexity rather than too long.

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?

With four required parameters, no annotations, no output schema, and thin schema descriptions, the definition is under-specified for an agent to invoke it reliably. Critical details — credential expectations, path resolution, overwrite semantics, and the shape of the result — are absent everywhere.

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 only 25%: only instance_id is documented in the schema, and the description adds no per-parameter meaning at all. It does not clarify how local_path and remote_path are resolved (absolute vs. relative to home), nor expand on the upload/download direction beyond what the enum already states, so the undocumented parameters are left unexplained in both places.

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 gives a specific verb+resource pair ('Transfer a file via SCP') and scopes it to managed instances, which cleanly separates it from the S3 siblings (s3_upload_object, s3_download_object) that move objects to buckets rather than to instances. It does not, however, name or contrast any sibling explicitly, so an agent must infer the boundary.

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 single sentence offers no when-to-use or when-not-to-use guidance and no alternatives. Nothing tells the agent whether this is preferred over run_command with scp/rsync, or what preconditions (instance reachability, credentials) must hold before calling it.

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