put_files

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns a metadata array and that files share did/sid but have independent fids. However, it does not mention potential errors, size limits, permissions, or idempotency, which are important for a batch upload tool.

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 dense sentence that conveys key information efficiently. It is front-loaded with the primary action ('batch upload multiple local files'). However, it could be slightly restructured for better readability.

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 an output schema, the description adequately explains the return type (array of metadata JSON objects). However, it omits important context like error handling, file size limits, or prerequisites, which are needed for a complete understanding of the tool's behavior.

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% (both 'files' and 'bucketName' have descriptions). The description adds value by explaining batch behavior and the output format, which is not in the schema. This elevates understanding beyond the schema alone.

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 in batch, sharing the same did/sid, with each file generating its own fid, and returning an array of metadata JSON objects. This distinguishes it from sibling tools put_file and put_stream. However, the terms 'did/sid' are not explained, slightly reducing clarity.

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 usage for batch uploads via the word '批量' (batch), but provides no explicit when-to-use or when-not-to-use guidance compared to the sibling tools put_file (single file) and put_stream (streaming). The context is clear but lacks exclusions or alternatives.

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