calendar_list_events

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses little. It does not state that this is a read-only operation, how results are ordered, whether recurring events are expanded, what the default time range is when timeMin is omitted, or whether results are paginated beyond maxResults.

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?

A single front-loaded sentence with no filler. It is efficiently sized, though the brevity comes at the cost of the missing context noted elsewhere rather than being optimally informative.

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 tool with four optional parameters, no annotations, and no output schema, the description is too thin. An agent still cannot tell what a result object looks like, whether nextPageToken exists, or what range 'upcoming' covers, all of which the description should have supplied given the absence of structured support.

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 every parameter (timeMin, timeMax, calendarId, maxResults) is already documented with format hints and defaults. The description adds no additional parameter meaning, so the baseline 3 applies.

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?

States a specific verb (List) and resource (events from Google Calendar) with a scope qualifier ('upcoming'). It is distinguishable from calendar_create_event, calendar_update_event, and calendar_delete_event by the verb alone, though the description never explicitly contrasts them.

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?

No guidance on when to use this versus the other calendar siblings, and no mention of the default time window implied by 'upcoming'. The agent must infer from the schema that timeMin/timeMax are optional and that omitting them yields some default range.

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