upload_folder

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

With no annotations provided, the description must fully disclose behavioral traits. It states that it creates folder structure and imports flows, but lacks details on side effects (e.g., overwrite behavior, conflict resolution, required permissions, supported archive formats, and error handling). For a mutation tool, this is insufficient.

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 concise with two sentences. The first sentence states the primary action, and the second provides necessary input details. No unnecessary words or repetition. Well-structured and front-loaded.

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 absence of output schema and annotations, the description is somewhat minimal. It covers the core functionality but lacks important context such as supported archive formats, max file size, effect on existing data, and potential errors. Among many sibling tools, it partially clarifies its role but could be more 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%, with both parameters described. The description adds minimal extra meaning by reiterating 'base64-encoded file content and filename'. It does not provide additional constraints like archive format, max size, or encoding specifics, so the description adds little beyond the schema.

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 a folder from a compressed archive, creates folder structure, and imports all flows. It distinguishes itself from sibling tools like upload_file, upload_project, and download_folder by focusing on folder structure creation and flow import.

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 mentions providing base64-encoded file content and filename, which implies the expected input format. However, it does not explicitly state when to use this tool over alternatives (e.g., upload_file for single files, upload_project for projects). Usage context is implied but not clearly defined.

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