delete_emails

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action is a move to Trash and recoverable, which is transparent, but omits details like authorization requirements, side effects, or error handling.

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 concise with two sentences, front-loading the core action and key characteristic ('soft delete, recoverable'). Every sentence adds value without 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?

For a simple tool with two parameters and no output schema, the description covers the essential behavior. However, it lacks details on return values, error conditions, or whether UIDs are global or folder-specific, leaving minor gaps.

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 provides descriptions for both parameters (uids and folder), covering 100% of the schema. The description adds that UIDs are permanent identifiers, which is helpful but not essential beyond the schema's description of 'Array of UIDs to delete'.

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 specifies the action ('Move emails to Trash folder'), the method ('using UIDs'), and the nature ('soft delete, recoverable'), distinguishing it from permanent deletion or archiving. This differentiates it from sibling tools like archive_emails and move_emails.

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 implies that the tool is for soft deletion via UIDs, but does not explicitly state when to use it versus alternatives like 'archive_emails' or 'move_emails' for moving to custom folders. No direct guidance on exclusions or prerequisites is provided.

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