drive_delete_file

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose that deletion moves to recycle bin (non-permanent), which is valuable. However, it omits other behavioral aspects such as permission requirements, impact on shared links, or error handling, leaving some gaps.

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, concise sentence that front-loads the purpose and includes a meaningful behavioral qualifier. Every word earns its place, with no redundancy or unnecessary detail.

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 delete tool with fully documented parameters, the description covers the essential behavioral context (move to recycle bin) and resource scope. It does not explain return values or errors, but these are not critical for a straightforward delete operation. Slightly incomplete but sufficient.

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 'type' and 'file_token' adequately described. The description adds no further parameter-specific details, so it does not enhance beyond the schema. Baseline 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 '删除云空间中的文件或文档（移至回收站）' explicitly states the action (delete), the resource (files/documents in cloud space), and adds a key qualifier (move to recycle bin). This clearly distinguishes it from sibling delete tools like wiki_delete_node, which targets wiki nodes.

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 implies usage for cloud drive files but provides no explicit guidance on when to use this tool over alternatives (e.g., wiki_delete_node for wiki nodes) or any exclusions. The context is clear but lacks direct comparison or when-not-to-use guidance.

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