创建文件夹

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

The annotations already convey the key safety traits (readOnlyHint=false, destructiveHint=false). The description adds the return value (new folder ID) but does not disclose additional behavioral context such as required permissions, duplicate name handling, or error conditions.

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 and front-loaded with the purpose. The parameter list is clear but duplicates schema info and omits the third parameter, so it is not perfectly efficient.

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 simplicity of the tool, the description covers purpose, parameters, and return value. However, it ignores the response_format parameter and provides no context on where to obtain parentId or any operational prerequisites, leaving gaps for a smooth 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%, with descriptions for all parameters. The description restates parentId and folderName but omits the response_format parameter entirely, adding no meaning 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's function: '在云盘中创建新文件夹' (create a new folder in cloud drive). It uses a specific verb plus resource and is easily distinguished from sibling tools like rename/delete/list folders.

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?

Usage is implied by the name and description (create a folder when needed), but there is no explicit guidance on when to use this tool versus alternatives, nor any mention of prerequisites like obtaining parentId from folder list tools.

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