List Calendar Events

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

Annotations already indicate a safe read-only operation. The description adds useful behavioral context: default values for max_results, single_events, order_by, and response_format, along with the return structure (title, time, location, attendees). This goes beyond the minimal safety profile.

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 well-structured with Args, Returns, and Examples sections. It is slightly repetitive of schema defaults but remains efficient and front-loaded with the core purpose. Examples earn their place by clarifying parameter combinations.

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 9-parameter tool with no output schema, the description covers all parameters, provides a return-value summary, and gives practical examples. It is complete enough for an agent to select and invoke the tool correctly, though it lacks explicit error-handling or auth notes.

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?

Input schema covers 100% of parameters with descriptions, so baseline is 3. The description reinforces parameter meaning by repeating key defaults and providing illustrative examples (e.g., time range format, query usage), adding practical value beyond the schema.

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 'List events from a calendar within an optional time range' with a specific verb and resource scope. It distinguishes from sibling tools like calendar_get_event (single event) and calendar_freebusy_query.

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?

Provides concrete examples ('Today's events', 'Search meetings', 'Next 7 days') that illustrate common usage. However, it does not explicitly contrast with alternatives or state when not to use this tool.

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