dingtalk_drive_mkdir

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

No annotations are present, so the description bears the full burden of behavioral disclosure. It only says 'create a new folder' and omits important behavioral details such as permission requirements, duplicate name handling, parent folder defaults, or whether the operation is idempotent.

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, direct Chinese sentence with no redundant wording or filler. It front-loads the core action effectively and is appropriately sized for the tool's simplicity.

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?

For a simple mkdir tool, the description plus schema is minimally adequate, but it leaves gaps: no return value description, no mention of where the folder is created if parent_id is omitted, and no error or permission context. These gaps are notable given there is no output schema or annotations.

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?

The input schema covers both parameters (name and parent_id) with descriptions, and the schema description coverage is 100%. The description adds no additional semantic value beyond what the schema already provides, so the baseline of 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 specific action ('在钉盘中创建新文件夹' = create a new folder in DingTalk Drive) and distinguishes it from sibling drive tools like list, info, and download. The verb and resource are explicit and match the tool name.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention how parent_id behaves (e.g., root folder default). It only gives the bare action, leaving usage context entirely to the schema.

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