calendar list events

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description usefully adds that timestamps use RFC 3339 with an offset and that single_events expands recurring events and orders by start time, though it omits pagination behavior.

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 sentences, front-loaded with the core purpose, then time formatting and one important behavioral flag. There is no wasted text.

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?

The description covers the core listing operation, timestamp format, and single_events behavior, and an output schema exists for return values. However, with seven parameters and no schema descriptions, it should document more parameter meanings, especially query, page_token, calendar_id, and max_results.

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 explain parameters. It clarifies time_min/time_max formatting and single_events semantics, but leaves query, page_token, calendar_id, and max_results undocumented.

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 and resource: list calendar events within a time range. It is clear enough to distinguish from calendar_get_event and calendar_list_calendars, though it does not explicitly name sibling alternatives.

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 phrase 'List events in a time range' implies the main use case, but the description gives no explicit guidance on when to use this instead of calendar_get_event, calendar_query_freebusy, or other calendar tools.

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