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. It partially compensates by describing the return content (filters, actions, run history), but omits explicit safety declarations (read-only status), pagination behavior, or permission requirements that would be essential for a complete behavioral picture.

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 a single, efficient sentence with no wasted words. Every phrase earns its place: 'List all saved rules' establishes the operation, while 'with their filters, actions, and run history' provides necessary specificity about the data richness without redundancy.

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 tool has no parameters, no annotations, and no output schema, the description adequately compensates by hinting at the return structure through the field enumeration (filters, actions, run history). However, it could be improved by noting the read-only nature or pagination limits given the lack of annotations.

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?

The input schema contains zero parameters, which establishes a baseline score of 4 per the scoring rules. The description appropriately does not mention parameters since none exist, and the schema coverage is 100% (trivially, as there are no parameters to document).

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 ('List') and resource ('saved rules'), and distinguishes from siblings by specifying the detailed scope includes 'filters, actions, and run history' rather than just rule names or IDs. This clearly differentiates it from create_rule, delete_rule, and run_rule.

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?

While the description implies this is for inspection/auditing of existing rules (vs. creating or running them), it provides no explicit when-to-use guidance or mention of alternatives like create_rule. The agent must infer usage context from the verb 'List' and the detailed field descriptions.

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