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

The annotations already declare destructiveHint=true, so the description's 'Delete' adds no new safety information. It does add a small behavioral nuance ('one or more folders') but fails to disclose whether deletion is recursive, whether folders must be empty, or any effects on child items. Given the annotation covers destructiveness, this minimal addition earns a low score.

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 five-word sentence with no fluff. It is immediately clear and front-loaded with the action. Every word adds essential meaning; 'one or more' is a concise scope qualifier.

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 destructive action with no output schema, this description is too thin. It does not clarify whether deletion is recursive, whether empty folders are required, or how errors are handled. The annotation covers destructiveness, but the agent still lacks enough context to safely invoke the tool in many real-world scenarios.

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 0%, and the description does not compensate. It repeats 'folders' but never explains what the 'folder' parameter should contain (path? ID? comma-separated list?). The 'one or more' phrasing hints at multiplicity but gives no syntax. This is a critical gap for successful invocation.

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 a specific action ('Delete') on a specific resource ('folders'), and it names the singular sibling tool 'delete_file' by contrast. It also conveys multi-target capability with 'one or more', which adds useful scope. This effectively distinguishes it from related tools like create_folder and move_folder.

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?

There is no guidance about when to use this tool versus alternatives such as delete_file or empty_queue. No prerequisites, exclusions, or mention of context in which deletion is appropriate. The description only states what it does, not when to choose it.

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