delete_folder

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

With no annotations provided, the description carries the full behavioral burden. It clearly discloses that deleting the folder does not delete the messages inside and that they will appear in their normal Inbox/Sent view. This goes beyond a generic 'delete' statement and helps the agent predict consequences accurately.

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?

Two sentences, zero filler. The main action is stated first, followed by the key exception about mail retention. Every sentence earns its place.

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 three-parameter delete operation with no output schema and 100% schema coverage, the description covers the essential context: what is deleted and what is not. It doesn't mention irreversibility, but that is generally implied for delete operations and the schema already tells the agent where to get the id.

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 schema provides 100% coverage, including an explanation of id ('from list_folders') and clear examples for domain and localPart. The description adds no new parameter-specific information, so the baseline score of 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 opens with the specific verb 'Delete' and the resource 'a custom folder', immediately distinguishing this tool from message or mailbox deletion. It also adds a clarifying contrast ('Does not delete the mail in it'), which eliminates ambiguity about what is actually removed.

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 makes the tool's scope clear: it deletes custom folders only, and tells the agent what will happen to contained messages. While it doesn't explicitly name alternatives like delete_message or create_folder, the context of custom folders and the folder-specific behavior makes the appropriate usage obvious.

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