delete_item

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

No annotations provided, so description must fully disclose behavior. It doesn't mention that items are moved to recycle bin (only in parameter description), nor any authorization needs or confirmation requirements. The agent might incorrectly assume permanent deletion.

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?

Single sentence, 13 Chinese characters, no fluff. Every word is meaningful. Ideal conciseness for a straightforward delete operation.

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?

No output schema, no annotations. Description doesn't mention return values (e.g., success, error handling) or what happens with non-existent paths. For a simple tool this is insufficient; agent lacks info on outcome.

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%, so baseline 3. Parameter descriptions add meaning (paths: list, move to trash; show_hidden: boolean). Main description adds nothing beyond schema, but schema already adequately describes 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?

Description clearly states it deletes files/folders on zspace NAS, supporting personal and team space paths. However, it omits that deletion is to recycle bin (only mentioned in parameter description). Verb 'delete' is clear and resource is specific, but could be more precise about the recycling behavior.

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?

No guidance on when to use this tool versus alternatives like move_item or create_file. No prerequisites or context about when it's appropriate to delete items. The description lacks any usage direction.

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