delete_folder

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

No annotations are provided, so the description carries full responsibility. It explicitly warns that deletion is destructive, describes server-dependent behavior on non-empty folders with RFC reference, and recommends user approval via the MCP client.

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 concise with two focused sentences and a warning block. Every sentence adds unique value: the action, the destructive nature, server dependency, and a user approval recommendation.

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?

The description covers key behavioral aspects like destructiveness and server dependency, which is good for a simple tool with no output schema. However, the lack of parameter documentation limits its completeness for an agent needing to format the folder identifier.

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 a single required 'name' parameter with no description. The description does not clarify whether this is a folder name, path, or ID, leaving ambiguity despite 0% schema coverage.

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 'Delete a mail folder,' which is a specific verb+resource combination. It is distinct from sibling tools like delete_email or bulk_delete, which target emails rather than folders.

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 a warning about destructiveness and server-dependent behavior, implying caution. However, it does not explicitly contrast with other tools like empty_trash or rename_folder, nor does it specify when to use or not use this tool.

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