List calendar events

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

With no annotations, the description carries the full behavioral burden; it accurately signals a read-only listing operation and the optionality of time/query filters. However, it does not disclose default behavior such as default calendarId, default maxResults, or that events are returned for a default time range starting now, leaving some behavior for the agent to infer.

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 a single front-loaded sentence with no redundancy; it conveys the core operation and optional filters in minimal space.

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 simple read-only listing tool with fully documented parameters, the description plus schema covers the essential information an agent needs. It could be marginally more complete by naming common sibling alternatives or clarifying return contents, but neither is required for correct invocation.

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 description coverage is 100%, so the six parameters are already fully documented in the input schema. The description only restates the filtering concepts (time range and query) rather than adding new semantic detail about parameter values or interactions.

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 names a specific action, 'List upcoming events in a calendar,' with optional filters, which clearly tells an agent what the tool does. It is distinct from sibling calendar event create/get/update/delete tools, though it does not explicitly contrast with the sibling get_event for single-event retrieval.

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?

'Optionally filtered by time range or query' implies when the tool is useful, but there is no explicit guidance about when to prefer this over google_calendar_get_event or google_calendar_list_calendars, nor any exclusions or prerequisites such as needing an account or calendarId.

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