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 burden of behavioral disclosure. It adds the 'upcoming' filter, which is not present in the schema, but it does not mention pagination, timezone handling, or whether recurring events are expanded. This is a modest addition beyond the schema.

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 sentence with no redundant phrases. It is front-loaded with the verb and resource, making it immediately clear what the tool does.

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 there are 3 parameters, no annotations, and a schema coverage of 0%, the description is too sparse to provide complete context. It omits essential details about the required 'account' parameter and the behavior of 'max_results', leaving the agent uncertain about how to use the tool correctly.

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 0%, so the description must compensate. It does not explain the meaning of 'account', 'calendar_id', or 'max_results' beyond what parameter names suggest. The 'account' parameter is especially ambiguous, and max_results' default limit is not mentioned.

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 it lists upcoming events, using a specific verb ('list') and resource ('events on a calendar'). This distinguishes it from sibling tools like calendar.create_event and other domain tools (gmail, drive).

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 implies usage for viewing future events but provides no explicit guidance on when to use it versus alternatives such as calendar.create_event. There are no exclusions or alternative tool mentions, so the usage context is only implicit.

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