List events in a time range

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

Beyond the read-only and idempotent annotations, the description discloses important behavior: recurring events are expanded into individual occurrences with independent ids, the default window is the next 30 days, and the source can be all visible calendars or named ones. This adds meaningful operational 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?

Three concise sentences, each earning its place: the core behavior, the notable recurring-event expansion, and the default time window. Information is front-loaded and there is no filler.

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 rich input schema, present output schema, and strong annotations, the description covers the key behavioral aspects an agent needs. Pagination and timezone details are left to the schema, which is acceptable, though a brief mention of cursor continuation could have been helpful.

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 provides 100% parameter descriptions, so the baseline is 3. The description adds general context about time ranges and calendar scoping, but does not add per-parameter details beyond what the schema already explains.

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 the tool lists events in a time range, with an explicit scope ('every calendar this server may see or from the ones named'). It is easily distinguishable from single-event tools like get_event, though it does not explicitly differentiate itself from search_events.

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 implies when to use the tool: listing events over a window, especially with recurring occurrences expanded. However, it provides no explicit guidance about when to prefer search_events or get_event, and gives no exclusions or alternative conditions.

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