empty_folder

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

Describes behavior: irreversible deletion of all messages, returns count. Explains two-step confirmation flow with preview. With no annotations, description carries full burden and covers key behavioral traits, though doesn't detail permissions or side effects.

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?

Four sentences, all essential. Front-loaded with main action. No fluff or repetition. Highly concise and well-structured.

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 tool with no output schema, description covers parameters, return value, and usage caveats. Could mention output schema explicitly but not needed. Lacks explicit alternatives, but otherwise complete.

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% with descriptions. Description adds value by explaining preview flow for 'confirmed' parameter and giving examples for 'folder' (e.g., 'Trash', 'Spam'), going beyond schema.

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 the tool's purpose: 'Permanently delete ALL messages in a folder.' It specifies the resource (messages in a folder) and action (delete), and notes irreversibility. This distinguishes it from siblings like delete_folder or trash_email.

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 usage context: only available when PROTONMAIL_ALLOW_EMPTY_FOLDER=true, typical use for Trash/Spam, and caution. However, it does not explicitly state when not to use or mention alternative tools like delete_folder or bulk_delete for partial deletion.

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