confirm_empty_folder

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

With no annotations provided, the description fully discloses the destructive outcome ('Deletes all messages') and enumerates specific error conditions (invalid, expired, already used token, or folder change). This is transparent about behavior and consequences.

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 brief, front-loaded with the main action, and every sentence serves a purpose: action, effect, and error conditions. No wasted 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 description covers the core workflow, success/error returns, and prerequisites. It doesn't mention permission requirements or what happens to the folder metadata, but for a confirmation tool, the essential context is present. Slight gap is acceptable given low complexity.

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 the baseline is 3. The description adds valuable meaning: token_id comes from prepare_empty_folder and folder_id must match the prepare step, which goes beyond property descriptions in the 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 action ('Confirm and execute emptying a mail folder') and the specific resource (folder) plus the required token from prepare_empty_folder. It distinguishes itself from sibling confirmation tools like confirm_delete_folder by explicitly tying to the prepare step.

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?

It clearly implies the tool should be used after prepare_empty_folder by mentioning the token requirement. It does not explicitly list when not to use it, but the context is strong enough to guide selection among sibling tools.

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