connect_icloud

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

Discloses the app-specific password requirement, validation before saving, and the return value, adding important context beyond the minimal annotations. This helps the agent set user expectations and understand preconditions.

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 concise sentences, each adding essential information: the action, the password requirement, validation, and return value. No wasted words.

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 two-parameter connection tool with an output schema, the description covers all necessary behavioral aspects: what it does, required credentials, validation, and return. It is fully sufficient for an agent to invoke 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?

With 0% schema coverage, the description explains the app_specific_password parameter in detail and implies the meaning of apple_id. It partially compensates for the missing parameter descriptions, though it could be more explicit about apple_id.

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 uses a specific verb ('Connect') and explicitly identifies the resource ('Apple iCloud calendar'), clearly distinguishing it from sibling tools like connect_ics and list_connections.

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 clearly states the tool's purpose, implying when to use it (for iCloud calendars). It does not explicitly contrast with alternatives like connect_ics, but the context is unambiguous enough for an agent to choose correctly.

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