List Calendar Events

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

Annotations indicate a read-only, idempotent operation. The description adds behavioral context beyond annotations, such as expanding recurring events (single_events), pagination (page_token), and output format options. No contradictions with annotations.

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 front-loaded with a one-sentence summary, then parameter list, returns, and examples. It is informative and each section is useful, but the length could be slightly trimmed for conciseness. Still, it's well-structured and efficient for the number of parameters.

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?

With 9 parameters and no output schema, the description covers all important aspects: parameter details with examples, return value specification, pagination, time ranges, and recurrent events. It is thorough for a listing operation.

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?

Schema coverage is 100%, but the description adds significant value by grouping parameters, explaining defaults, providing format details, and including examples (e.g., ISO 8601 time format, sort order options). This goes well beyond the schema's field 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 'List events from a calendar within an optional time range,' specifying the verb (list), resource (events from a calendar), and scope. It distinguishes from sibling tools like calendar_get_event (single event) and calendar_list_calendars (list calendars).

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 detailed parameter usage and examples (e.g., today's events, search meetings, next 7 days), giving clear context for when to use each parameter. However, it does not explicitly state when not to use this tool or mention alternative tools like calendar_freebusy_query for free/busy data.

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