Mail Delete Message

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

The annotations already show destructiveHint=true and idempotentHint=false, but the description adds zero behavioral context beyond that. It does not mention permanence, confirmation prompts, permission requirements, or any side effects of deleting a message.

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 short sentence, but it is under-specified rather than concise. It adds no information beyond what the tool name already conveys, so the brevity is not earned.

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 destructive operation with a single required parameter and no usage details, this description is severely incomplete. It lacks any explanation of what the deletion affects, how to obtain message_id, what the output contains, or what safeguards or permissions apply.

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 description coverage is 0%, and the description provides no meaning for the single 'message_id' parameter. The agent can only guess that it identifies the message to delete; there is no guidance on format, source of the ID, or constraints.

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 merely restates the tool name ('mail_delete_message') and labels it as a delegated Apple domain tool exposed through Apple-Tools-MCP. It never explicitly states that it deletes a mail message or what resource it acts on, so the agent must infer the entire purpose from the name.

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 about when to use this tool instead of siblings like mail_move_message, mail_archive_message, or mail_mark_message. No context, no exclusions, and no scenarios are provided.

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