prepare_delete_folder

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

With no annotations, the description carries the full transparency burden. It discloses the return of a preview with message count, an approval token, token expiry after 5 minutes, and error behavior for non-existent folder IDs. It implicitly conveys that no deletion occurs until confirmation, but doesn't mention potential permission requirements.

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?

Three concise sentences: purpose, return/next step, and error/expiry. Front-loaded with the main purpose and zero 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?

Despite no output schema, the description explains the response (preview with message count, token), the necessary next action, error behavior, and token expiry. For a simple single-parameter tool, this is fully 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?

The schema already provides a complete description for the single folder_id parameter (e.g., from list_folders). The tool description adds no additional parameter-level details, so it meets the baseline for high schema coverage.

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 prepares to delete a mail folder and all its messages, with a preview and approval token. It distinguishes itself from confirm_delete_folder and other folder operations like prepare_empty_folder by specifying it's a preparatory step for deletion.

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 explicitly instructs to call confirm_delete_folder with the token to execute, making the usage flow clear. It doesn't explicitly mention alternatives or exclusions, but the context is well-defined for a two-step delete operation.

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