delete_folder

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

The annotations already mark the tool as destructive (destructiveHint=true) and not read-only. The description adds a crucial behavioral detail: deletion is not permanent but moves the folder to Deleted Items. This goes beyond the annotation's binary safety flag, providing recovery context.

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, direct sentence that is front-loaded with the action and resource. No unnecessary words.

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 tool is simple, with one parameter and no output schema. The description covers the core function and the key nuance of moving to Deleted Items. While it omits details about consequences for contained messages or folder hierarchies, the core usage is clear and the description complements the annotations well.

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?

Input schema has one required parameter, folder_id, and the description does not elaborate on its meaning or format beyond the schema's type/title. With 0% schema description coverage, the description fails to compensate by explaining what folder_id identifies or how to obtain it.

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 uses the specific verb 'Delete' and identifies the resource as 'mail folder', and further clarifies the behavior by noting it moves to Deleted Items. This clearly distinguishes it from sibling tools like create_folder and rename_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?

The description provides no explicit guidance on when to use this tool versus alternatives, such as using move_message for individual emails or permanent deletion. The context is clear from the purpose, but no exclusions or alternative conditions are stated.

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