calendar_list_events

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses that expanded occurrences require explicit offset-bearing timeMin/timeMax and that singleEvents:false reads underlying masters and exceptions. These are non-obvious behaviors that improve transparency.

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 two sentences, front-loaded with the primary purpose, and uses precise, non-redundant language. It efficiently conveys the core function and key edge cases without unnecessary detail.

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 tool's complexity and lack of an output schema, the description covers essential behavior for listing and searching events, including recurrence handling. It omits details about pagination and output format, but these are not critical for invocation and are partially covered by parameters like cursor and pageSize.

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 description explains the semantics of timeMin/timeMax and singleEvents, but the input schema has no property descriptions and the other seven parameters (accountId, calendarId, query, showDeleted, pageSize, cursor) remain undocumented. Since schema coverage is 0%, the description only partially compensates.

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 or searches events using query text in one selected calendar, with a verb, resource, and scope. It also differentiates from siblings by noting singleEvents:false reads underlying masters and exceptions, which distinguishes it from calendar_list_instances and calendar_get_event.

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 behavioral hints for when to use singleEvents:true vs false and requires offset-bearing time bounds for expanded occurrences. However, it does not explicitly name alternative tools or state 'use this instead of X', leaving some inference to the user.

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