calendar_list_events

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

With no annotations, the description carries the full burden. It does not disclose key behaviors like pagination (pageToken), default time range (timeMin defaults to now), or that it returns only upcoming events by default. The term 'upcoming' is ambiguous without defining the time window.

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 very short (one sentence), which is concise but at the expense of useful details. For a 7-parameter tool, a slightly longer description would improve usability without losing conciseness.

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?

Without an output schema, the description should explain return value structure (e.g., list of event objects). It does not mention pagination, filtering, or the fact that results are limited by maxResults. The description is insufficient given 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?

Schema coverage is 100%, so the schema already documents all parameters thoroughly. The description adds no additional meaning beyond saying 'List upcoming events'; it does not clarify parameter usage or relationships (e.g., how timeMin and timeMax define 'upcoming').

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 action (List) and the resource (upcoming events in a calendar), which distinguishes it from sibling tools like create or delete events. However, it could be more specific about the scope (e.g., time range) to further differentiate.

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 is provided on when to use this tool versus alternatives (e.g., calendar_get_event for single events). The description lacks context about when not to use it or what prerequisites are needed (e.g., a valid calendarId).

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