upload_assets_batch

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

Discloses automatic deduplication of file_path values and partial failure handling (continue_on_error). Advises resubmitting only failed files. No annotations provided, so description carries full burden; adequately covers key behaviors.

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?

Four sentences, all essential. First sentence states core purpose, second addresses dedup, third lists use cases and alternative, fourth gives error recovery guidance. No fluff.

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?

Covers all key aspects: batch upload, dedup, large file alternative, partial failure handling, and hints at parameter dependencies. With no output schema, the description sufficiently prepares an agent for correct invocation.

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 coverage is 100%, baseline 3. Description adds value by explaining dedup behavior for files, default parallelism, default continue_on_error, and additional context for block_type (MIME validation, storage path) and conditional fields (variant_name, etc.).

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?

Clearly states batch upload multiple files to a single block. Distinguishes from individual upload tool upload_asset via large file guidance. Mentions specific use cases (logos, visuals, etc.) that align with block_type enum.

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?

Provides when to use (batch) and when not (large files >50MB, use upload_asset). Includes retry guidance on partial failure. Does not explicitly exclude single-file uploads but context implies batch is for multiple files.

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