Mail Compose Draft

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

The annotations include openWorldHint=true, idempotentHint=false, and destructiveHint=false, but the description adds no behavioral context such as whether this creates a draft, opens a compose window, requires permissions, or has side effects. The description's only content is organizational boilerplate.

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 brief, but brevity here is under-specification, not conciseness. The single sentence conveys no actionable information and merely restates the tool's name and provenance.

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 seven parameters, no schema descriptions, and a rich set of sibling mail tools, this description is severely incomplete. It does not explain what a 'draft' means in this context, whether the email is sent or saved, or how this differs from mail_send_message. An agent has no basis for invoking it correctly.

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 does not compensate by explaining any of the seven parameters. The field names are somewhat self-explanatory, but the description itself adds no semantic value, and optional fields like from_account, attachments, and cc remain undocumented.

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 only restates the tool name and says it is a 'Delegated Apple domain tool' exposed through Apple-Tools-MCP. It does not state what the tool actually does—composing a mail draft is left entirely to inference from the name. There is no verb, resource, or behavior specified.

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 gives no guidance on when to use this tool, what it is for, or when to prefer alternatives like mail_send_message or mail_reply_message. An agent cannot determine the intended workflow from this text.

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