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 of behavioral disclosure. While 'Delete' implies destruction, the description fails to mention whether this operation is permanent, what happens if the rule doesn't exist, or whether it affects emails already processed by the rule.

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?

The description is extremely concise at six words with no filler. It front-loads the action ('Delete') and immediately specifies the scope ('a saved rule by name'), making it easy to scan.

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 string parameter, no output schema, no nested objects), the description is minimally sufficient. However, for a destructive operation with no annotations, it should include safety warnings or error condition notes to be fully complete.

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% with the 'name' parameter fully documented as 'Rule name to delete'. The description mentions 'by name' which aligns with the schema, but adds no additional semantic context (e.g., case sensitivity, whether it's the display name or internal ID) beyond what the schema already 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?

The description provides a clear verb ('Delete') and resource ('saved rule') and distinguishes from siblings like 'run_rule' or 'create_rule' through the action word. However, it doesn't explicitly clarify what constitutes a 'rule' in this email context or mention how it differs from bulk deletion tools.

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 offers no explicit guidance on when to use this tool versus alternatives like 'run_rule' or 'create_rule', nor does it mention prerequisites such as the rule needing to exist first. It states only what the tool does, not when to choose it.

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