prepare_delete_email

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

With no annotations, the description carries full burden and does exceptionally well. It discloses that the tool returns a preview and an approval token, specifies expiration behavior (5 minutes), clarifies that deletion is deferred to a follow-up call, and describes the error condition for invalid IDs. This gives the agent a clear picture of the tool's behavior and 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?

The description is three sentences, front-loaded with the main purpose, and each sentence provides distinct value: purpose, workflow, and error/expiration details. No filler 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?

Despite having no output schema, the description explains what the tool returns (preview and token), the token's expiration, the required follow-up action, and an error condition. For a simple preparation tool, this is complete and covers all essential contextual information.

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 input schema already fully describes email_id (type, format, example source), and schema coverage is 100%. The description adds context about error on non-existent ID but does not introduce new parameter meaning, so the baseline 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 clearly states the tool's function with a specific verb and resource: 'Prepare to delete an email (move to trash).' It distinguishes itself from the sibling tool confirm_delete_email by explaining this is the preparation step, and from prepare_batch_delete_emails by context (single 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?

The description explicitly instructs to 'Call confirm_delete_email with the token to execute the deletion,' providing a clear sequential usage. It also notes an error condition for non-existent IDs. However, it does not explicitly mention alternatives like prepare_batch_delete_emails for batch deletion, though the sibling name makes this implicit.

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