icloud-mcp

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

No annotations provided, so description carries full disclosure burden. States read operation ('List') and date range scoping, but omits output format details, pagination behavior, or what occurs when no events match. Adequate but minimal behavioral context.

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: first states purpose, second states prerequisite. Perfectly front-loaded and appropriately sized for the tool's 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?

For a 4-parameter listing tool with complete schema documentation, description is sufficiently complete. The prerequisite instruction is critical for successful invocation. Minor gap: does not describe return value structure (array of event objects?), though absence of output schema makes this less strictly required.

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?

Input schema has 100% description coverage, establishing baseline of 3. Description adds valuable workflow context for calendarId parameter ('from list_calendars'), but does not augment understanding of date range parameters (since/before) or limit beyond schema descriptions.

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?

Description uses specific verb 'List' with clear resource 'events in a specific iCloud calendar' and scope 'within a date range'. Effectively distinguishes from sibling operations like create_event, delete_event, and get_event (single retrieval).

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 explicit prerequisite 'Use list_calendars first to get a calendarId', establishing clear workflow. Lacks explicit differentiation from search_events (text search alternative) or guidance on when to use date range vs. other filtering methods.

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