icloud-mcp

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

No annotations provided, so description carries full burden. Mentions 'in sequence' execution and dryRun behavior, but omits critical mutation details: side effects of rules, error handling (fail-fast vs. continue), idempotency, and synchronous/asynchronous nature.

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. Front-loaded with purpose, followed immediately by usage hint. 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?

Adequate for a single-parameter tool, but given lack of output schema and annotations, description should ideally disclose success/failure signals or execution behavior. Sufficient for basic operation but leaves operational 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 has 100% coverage with dryRun fully documented. Description essentially repeats the schema definition ('preview all rules without making changes') without adding syntax details, examples, or edge cases. Baseline 3 appropriate when schema does heavy lifting.

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?

States specific verb (Run), resource (saved rules), scope (all), and execution pattern (in sequence). Clearly distinguishes from sibling 'run_rule' by emphasizing 'all' and sequential execution.

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?

Provides specific guidance on using dryRun for previewing changes, but lacks explicit comparison to sibling 'run_rule' or guidance on when to use single vs. bulk execution.

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