icloud-mcp

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

With no annotations provided, the description carries the full disclosure burden and succeeds in explaining: the destination folder, the non-destructive nature (no sending), content format support (plain text/HTML/multipart), and persistence/editability lifecycle. Missing only error handling and return value details.

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?

Three sentences with zero waste: sentence 1 defines the core action and constraint, sentence 2 covers format capabilities, sentence 3 explains persistence. Front-loaded with the most critical information (save without send).

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 the 100% schema coverage handling parameter semantics, the description adequately covers the tool's behavioral complexity (multipart email support, threading headers via inReplyTo/references). The only gap is the lack of output schema description, which would ideally clarify what identifier or confirmation is returned upon saving.

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%, establishing a baseline of 3. The description reinforces the content type parameters by mentioning 'plain text, HTML, or both' and implies the 'account' parameter's default ('iCloud Drafts folder'), but doesn't add syntax or validation details beyond the schema.

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 opens with a specific verb ('Save') and resource ('draft email'), clarifies the destination ('iCloud Drafts folder'), and explicitly distinguishes from siblings by stating it operates 'without sending it'—critical differentiation from the likely 'compose_email' sending tool.

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?

Provides clear context for when to use: when you want to save without sending and edit later from Mail.app or iCloud.com. The 'without sending it' phrase implicitly defines the alternative (immediate sending), though it doesn't explicitly name the sibling tool to use for that purpose.

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