email_delete

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

No annotations are provided, so the description must disclose behavioral traits. It states 'Delete' implying a destructive action, but does not clarify if deletion is permanent or moves to trash, whether a folder is required, or if authentication via email/password is needed. The description adds minimal context beyond the action.

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 sentence, efficient and to the point. However, it could benefit from additional structure, such as bullet points for parameters or a short note on behavior. Still, it's appropriately sized for a simple tool.

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?

Given 4 parameters and no output schema or annotations, the description is too sparse. It fails to explain required parameters beyond UID, return behavior, error scenarios, or authentication requirements. The tool is simple but the description leaves significant 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?

With 0% schema description coverage, the description should compensate for the undocumented parameters. However, it only mentions 'uid' and provides no meaning for 'folder', 'email', or 'password'. The description adds no value beyond the schema's parameter names.

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?

Description clearly states 'Delete an email by UID.' which combines a specific verb ('Delete') with a resource ('email') and identifier ('UID'). The purpose is unambiguous, but it does not distinguish itself from sibling tools like email_get or email_mark_read, which also operate on 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?

No guidance on when to use this tool vs alternatives (e.g., email_get, email_mark_read). No mention of prerequisites (e.g., needing the folder or credentials) or context for appropriate use. The description is entirely lacking in usage direction.

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