transfer_file

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

No annotations are provided, so the description must disclose behavioral traits like authentication needs, file size limits, overwriting behavior, or success/failure conditions. The description offers none of this, only stating the basic operation. It fails to inform the agent about important behavioral aspects.

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, which is concise, but it is so sparse that it omits essential information. A good description balances brevity with completeness; here the trade-off leans too far toward brevity, sacrificing clarity for a human or AI agent.

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 the complexity (4 parameters, no output schema, no annotations, only 25% schema coverage), the description is grossly incomplete. It does not explain what 'managed instance' means, how paths should be formatted, whether the tool supports recursive transfers, or what the output looks like. The agent lacks sufficient context to use the tool correctly.

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%, with only instance_id having a description. The tool description adds no clarification for other parameters such as direction, local_path, or remote_path. For instance, direction's enum values 'upload' and 'download' are not explained in context. The description does not compensate for the low schema coverage.

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 transfers files via SCP to or from managed instances. The verb 'transfer' and resource 'file' combined with protocol 'SCP' and scope 'any managed instance' makes the purpose unambiguous. Among siblings like s3_* or docker_*, this tool is distinct in its focus on SCP-based 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 implies the tool is for file transfer using SCP but provides no explicit guidance on when to use it versus alternatives, prerequisites, or contrasting contexts. The phrase 'to or from any managed instance' gives some context, but there is no mention of when not to use the tool or what other tools might be more appropriate.

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