prepare_empty_folder

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

With no annotations provided, the description carries the transparency burden. It discloses that the tool does not delete yet (prepares), returns a preview and token, that the token expires after 5 minutes, and that invalid IDs return an error. This goes beyond basic descriptions of similar tools.

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?

Description is three sentences, front-loaded with purpose, then return value and next step, then error/expiry. Every sentence earns its place with no redundancy or irrelevant detail.

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 prepare step with no output schema, the description covers the essential context: preview, approval token, next step (confirm tool), error handling, and token expiration. This is sufficient for an agent to invoke the tool and understand the expected flow.

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 single parameter folder_id is fully documented in the schema (description: 'The folder ID to empty (e.g., from list_folders)'). The description adds only the error behavior for invalid IDs, which is not parameter semantics. With 100% schema coverage, a 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 states a specific verb and resource: 'Prepare to empty a mail folder by deleting all its messages.' This clearly distinguishes it from sibling tools like confirm_empty_folder (which executes the deletion) and prepare_delete_folder (which deletes the folder itself).

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 explicitly instructs when to use the tool and the sequential flow: 'Call confirm_empty_folder with the token to execute.' It also notes an error condition (invalid folder ID). It doesn't explicitly exclude alternatives, but the two-step pattern is clear.

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