icloud-mcp

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

No annotations are provided, so the description carries the full burden. While 'Move' implies a write operation, the description fails to disclose critical behavioral traits for a bulk operation: whether moves are reversible, what the dryRun behavior returns, success/failure handling, or performance implications of large batches.

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?

Two sentences with zero waste: first sentence establishes core function, second establishes architectural relationship to sibling tool. Every word earns its place.

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 lack of annotations and output schema, the description is minimally adequate for a 4-parameter tool, but lacks important context for a bulk mutation operation (e.g., return value description, safety warnings). It meets baseline requirements but has clear 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?

Schema description coverage is 100%, so parameters are well-documented in the schema itself. The description adds context that this is a 'wrapper' which helps understand the domain parameter's filtering role, but does not add syntax details, format constraints, or examples beyond what the schema provides.

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 the specific action (move), resource (emails), scope (from a specific domain to a folder), and explicitly identifies itself as a 'convenience wrapper around bulk_move with a domain filter,' effectively distinguishing it from the general bulk_move sibling.

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 'convenience wrapper' statement implies this tool is for domain-specific filtering versus the general bulk_move, providing implicit context. However, it lacks explicit when-to-use guidance compared to siblings like bulk_move_by_sender or warnings about irreversible operations.

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