batch_delete_files

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

With no annotations provided, the description carries full responsibility for disclosing behavioral traits. It merely states the function without mentioning important behaviors such as: whether deletion is permanent, if folders are deleted recursively, what happens on error, or how the 'force' parameter affects execution. This is insufficient transparency for a destructive operation.

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 extremely concise—just six Chinese characters. While brevity is positive, it sacrifices essential details. A minimally adequate description should include more context, such as the effect of the 'force' parameter or a note about recursive deletion. The structure is a single sentence, which is acceptable but lacks front-loading of critical information.

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 tool's complexity (batch deletion with optional force) and the absence of an output schema, the description is incomplete. It does not explain return values, error handling, or side effects like permanent data loss. A more complete description would cover these aspects to properly inform the agent.

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 has 100% description coverage for both parameters ('paths' and 'force'), so the schema already explains their meaning. The tool description adds no additional context beyond the schema. The baseline score is 3, as the description does not detract but also does not enhance understanding of parameters.

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 purpose: batch deletion of files or folders. It distinguishes this from sibling operations like batch_copy_files, batch_create_files, and batch_move_files by specifying deletion. The verb 'delete' and resource 'files or folders' are specific and unambiguous.

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 over alternatives (e.g., delete_file for single files, or other batch operations). It does not mention prerequisites, conditions, or when not to use it. This leaves the agent without context for appropriate selection.

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