batchUploadFiles

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

No annotations are provided, so the description carries full burden. It implies a write operation but does not disclose behavior such as overwrite policy, error handling, partial success, or permission requirements. The minimal description lacks behavioral transparency.

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 with no redundant words. It is front-loaded and to the point.

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 lack of annotations and output schema, the description should provide more context about the connectionId (required), success indicator, error scenarios, and details about batch behavior. It is insufficient for a batch operation tool.

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%, meaning the description adds no parameter info beyond the schema. The schema defines connectionId and files array with localPath/remotePath, which is self-explanatory. The description adds no extra meaning, but the schema is clear, so 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 clearly states the tool uploads multiple local files to a remote server. The verb 'Uploads' and resource 'local files to a remote server' are specific. It distinguishes from sibling tools like 'uploadFile' (singular) and 'batchDownloadFiles' (download direction). However, it does not explicitly contrast with 'uploadFile' or mention when to prefer batch over single.

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 guidance on when to use this tool vs alternatives (e.g., uploadFile). No prerequisites, context, or exclusions provided. The description offers no usage context.

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