Delete multiple emails at once by moving them to trash. Supply an array of email IDs to remove unwanted messages.
Delete multiple emails (move to trash)
| Name | Required | Description | Default |
|---|---|---|---|
| emailIds | Yes | Array of email IDs to delete |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Specifies the behavior 'move to trash', which is a key detail, but lacks disclosure of additional traits such as irreversibility, permission requirements, rate limits, or effect on trash retention. No annotations are provided, so the description bears full responsibility but only partially fulfills it.
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?
One short sentence that front-loads the core action and outcome. Efficient but could include more detail without losing conciseness.
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?
Adequate for a simple bulk operation with one parameter, but lacks information on partial success, error handling, or limits (e.g., maximum number of IDs). No output schema, so no return value explanation needed. Could be more complete for a bulk action.
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?
Schema coverage is 100%, so the schema fully describes the parameter. The description adds no new meaning beyond repeating 'multiple emails'. No extra context on array size limits, required format, or validation rules.
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?
Clearly states the action 'Delete multiple emails' and specifies it moves to trash, distinguishing it from permanent deletion. The tool name 'bulk_delete' is accurately reflected and differentiated from sibling 'delete_email' for single 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?
Implies use for deleting multiple emails, but no explicit guidance on when to use this tool over alternatives like 'delete_email' for single deletes or 'bulk_move' for moving to other folders. No prerequisites or constraints mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.