delete-mail-folder

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

Annotations already include destructiveHint=true, but the description adds crucial specifics: 'Deletes a mail folder and all its contents. This action is irreversible.' This goes beyond the annotation and helps the agent set expectations.

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 crisp sentences plus a tip. Front-loads the core action, then provides essential operational details (irreversibility, how to find ID). No fluff or redundancy.

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 operation with no output schema, the description covers what is deleted (folder + contents), irreversibility, how to specify the folder, and a pointer to a sibling tool for discovery. The confirm gate is covered in the schema, so nothing critical is missing.

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 is 3. The description adds value by mentioning that the folder can be specified by well-known name (not just ID), which the schema does not mention. This extra guidance pushes it above baseline.

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?

States a specific verb ('Delete') and resource ('mailFolder'), and clarifies it supports mailSearchFolder and how to specify via ID or well-known name. Clearly distinct from update/create/move siblings.

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?

Provides a tip to use list-mail-folders to find the folder ID, which aids usage. Does not explicitly discuss when to avoid this tool (e.g., if a soft delete is needed) or name alternative deletion methods, but the context is clear enough.

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