delete_emails

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

With no annotations provided, the description carries the burden of behavioral disclosure. It does disclose an important behavioral trait—the default soft delete via Trash versus permanent expunging—which is meaningful for a destructive operation. However, it does not mention potential side effects, authorization requirements, or what happens to the emails after expunging.

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 a single, efficient sentence with the key behavioral distinction front-loaded. Every word earns its place, and there is no redundant or filler content.

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 delete tool with well-documented parameters, the description is mostly adequate. However, with no annotations and no output schema, it omits details about return values, error handling, or confirmation of deletion, which an agent might need for confident invocation.

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 describes all three parameters (uids, folder, permanent) at 100% coverage, so the baseline is 3. The description adds the 'soft delete' framing, which clarifies the default behavior, but does not meaningfully expand on parameter meaning beyond what the schema provides.

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 clear verb ('Delete'), a clear resource ('emails'), and distinguishes the two core behaviors: moving to Trash (soft delete) versus permanent expunging. It does not explicitly name or differentiate sibling tools, such as move_emails, but the deletion intent is unambiguous.

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?

There is no guidance on when to use delete_emails versus alternatives like move_emails or mark_emails. The description implies general deletion usage but provides no context for choosing this tool, nor does it mention any caveats or exclusions.

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