calendar_list_events

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

Annotations already declare readOnly/openWorld/non-destructive, so the safety profile is covered. The description adds useful behavioral details not in the annotations: recurring events are expanded and the default time window is the next 7 days.

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?

Three short, information-dense sentences with no filler. The most important behavior (date range and default) is front-loaded, and every sentence contributes meaning.

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?

Core invocation logic is present: event listing, date range, default window, and recurrence behavior. However, there is no output schema and no mention of return shape, pagination, max_results implications, or query filtering, so an agent might still be uncertain about result handling.

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?

With 0% schema description coverage, the description must compensate. It explains time_min/time_max format (RFC3339) and the default range when empty, but it does not clarify query, profile, calendar_id, or max_results semantics, leaving several parameters under-specified.

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?

Names the specific action (list events), the resource (calendar events), and the scope (between time_min and time_max). The default behavior and recurrence expansion further disambiguate it from siblings like calendar_free_busy.

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?

Clearly states the common date-range usage and what happens when no dates are provided (next 7 days). It does not explicitly discuss when to prefer calendar_free_busy or drive_search, but the core usage context is clear.

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