icloud-mcp

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

No annotations provided, so description carries full burden. While 'Read' implies read-only safety, the description lacks explicit behavioral disclosures (idempotency, return format, rate limits, error conditions) that annotations would typically cover.

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?

Single sentence, 9 words, front-loaded with verb. No redundant phrases or unnecessary elaboration. Efficiently communicates core function without waste.

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 basic invocation given complete schema coverage, but gaps remain: no output schema hints (what fields returned?), no differentiation from 50+ siblings, and no iCloud-specific constraints or authentication notes.

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 has 100% description coverage, establishing baseline of 3. Description mentions 'pagination' which aligns with limit/page parameters, and 'iCloud inbox' which maps to the mailbox parameter, but doesn't add syntax details, validation rules, or semantic relationships beyond the schema definitions.

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?

Clear verb ('Read') and resource ('emails from iCloud inbox'). Mention of 'pagination' distinguishes from sibling 'get_email' (likely single fetch), though it doesn't differentiate from 'search_emails' or other bulk retrieval siblings.

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?

No explicit when-to-use guidance or alternative suggestions. With numerous siblings (search_emails, get_emails_by_sender, get_emails_by_date_range), the description fails to specify when this general pagination approach is preferred over specialized queries.

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