List Calendar Events

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

The description discloses critical behavioral traits beyond annotations: recurrences are expanded, there is no paging so 'total' is exact, and modifying recurring occurrences requires an explicit 'apply_to' in write tools. Annotations already confirm read-only and idempotent, and the description adds rich operational context without contradicting them.

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 three short, focused paragraphs. The first sentence delivers the core function, the second explains recurrence implications, and the third covers paging behavior and tuning. Every sentence earns its place with 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?

For a read-only listing tool, this description covers the essential behavioral quirks: recurrence expansion, exact totals due to no paging, and how to narrow results. The output schema exists, so return structure is already defined. The description is notably complete for the tool's complexity.

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?

All 5 parameters have thorough schema descriptions with 100% coverage. The main description adds cross-parameter context, such as 'the whole window is read every call' and how 'limit' acts as a safety cap, clarifying the interaction between start, end, and limit beyond the individual parameter 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 states exactly what the tool does: 'Calendar events in a time window, recurrences expanded.' This clearly distinguishes it from siblings like get_event (single event) and get_user_availability. The verb and resource are specific and unambiguous.

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 explicit context: 'There is no paging and nothing to page — the whole window is read every call' and advises 'Narrow the answer by moving start/end.' It also mentions an explicit alternative in the person parameter description: 'for anyone else use get_user_availability.' It lacks a direct 'when not to use' contrast with get_event, but the guidance is strong.

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