List Calendar Events

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

Beyond annotations (readOnlyHint, idempotentHint), the description adds caching specifics (5 min fresh, 30 min stale), force_refresh option, and confirms it is safe for unsupervised use. No contradictions.

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 well-structured with sections for caching, parameters, and returns. It is concise without unnecessary words. Slightly verbose due to full parameter listing, but this is justified given 0% schema coverage.

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 complexity (6 parameters, output schema exists), the description is complete. It covers caching, parameter details, safety, and return fields like _cache_status. The output schema covers event properties, so no additional detail needed.

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 has 0% description coverage, but the description manually documents all 6 parameters with defaults, ranges (1-365 for days_ahead, 1-200 for limit), and semantics (e.g., include_details for full event details). This fully compensates for the missing 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?

The description clearly states it lists upcoming calendar events from now until a specified number of days ahead. It uses specific verb-resource ('List Calendar Events') and distinguishes from siblings like search_events or calendar_get_event by focusing on upcoming events from a specific account.

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 provides context: it is read-only and safe for unsupervised use, and explains caching behavior. However, it does not explicitly state when not to use this tool or mention alternatives like calendar_get_event for single events or calendar_get_free_busy for availability checks.

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