list_events

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

No annotations, so description carries full burden. It discloses the large-result-volume risk, which is useful. However, the claim 'without filtering' directly contradicts the presence of optional time_range_start/end parameters, which by definition would filter the results. This ambiguity fails to clearly explain the effect of those parameters.

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?

Two tightly written sentences with no fluff. The critical warning is front-loaded, and the alternative is named explicitly. Every word earns its place.

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?

Good for a simple list tool: warns about volume, singles out calendar_query, and implies single-calendar scope. However, the conflicting statement about filtering leaves the time_range parameters' behavior unclear, and there is no mention of return format or pagination, which is a gap worth noting.

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 details both time range parameters. The description adds no additional insight about them, and the 'without filtering' phrasing actually muddies their meaning. Baseline 3 is appropriate given the schema covers everything.

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) + resource (ALL events from a single calendar) + scope (without filtering). It clearly distinguishes from the sibling calendar_query, which is mentioned as the alternative for filtered searches.

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?

Explicitly warns against using this tool for filtered searches and names the alternative (calendar_query) with its advantage (multi-calendar search). Provides clear when-to-use and when-not-to-use guidance.

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