icloud-mcp

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

With no annotations provided, the description carries the full burden. It discloses the critical safety trait that deletion is 'permanent' (irreversible), but lacks other behavioral details such as error handling when contactId doesn't exist, authentication requirements, or side effects.

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?

Seven words, one sentence. Every element earns its place: action verb, resource, system boundary, and safety warning ('permanently'). No filler or redundancy. Perfectly front-loaded and sized for the operation complexity.

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 low complexity (single required string parameter) and 100% schema coverage, the description adequately covers the operation's intent and critical safety warning. Lacks explicit mention of error states or success indicators, but sufficient for a simple destructive CRUD operation without output schema.

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%, with 'contactId' fully described as 'Contact ID to delete'. The description implies a single identifier is needed but adds no syntax details, format examples, or semantics beyond what the schema already provides, warranting the baseline score.

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 provides a specific verb ('Delete'), resource ('contact'), system context ('iCloud Contacts'), and scope modifier ('permanently'). It clearly distinguishes from siblings like create_contact, update_contact, and get_contact by specifying the destructive removal operation.

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 word 'permanently' implies this is for irreversible removal, but there is no explicit guidance on when to use this versus update_contact, or prerequisites like verifying the contact exists first. Usage is implied by the verb but not explicitly contextualized.

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