ftp_batch_upload

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

No annotations are provided, so the description carries full burden. It only mentions 'single operation' and performance, but fails to disclose critical behavioral traits such as atomicity, error handling for partial failures, ordering, authentication requirements, or rate limits.

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, front-loaded with purpose. Every word adds value: 'Upload a collection of local files to remote destinations in a single operation' is concise and informative. No redundancy.

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 simple batch upload with one parameter and no output schema, the description covers the basic operation and benefit. However, it omits expected return information (e.g., success/failure reporting, results metadata) and does not address potential constraints like maximum file count or size. Given the tool's simplicity, it is adequate but not fully complete.

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%, and the schema already documents the files parameter with localPath and remotePath. The tool description adds 'in a single operation' but does not enhance parameter meaning beyond that. Baseline 3 is 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 states 'Upload a collection of local files to remote destinations in a single operation' with a specific verb ('Upload'), resource ('collection of local files'), and scope ('remote destinations in a single operation'). This clearly distinguishes it from singular tools like ftp_upload and batch download ftp_batch_download.

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 explicitly recommends using this tool for multiple files to minimize connection overhead and improve performance. This gives clear when-to-use guidance, though it does not explicitly mention when not to use (e.g., single files) or alternative tools.

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