list_calendar_events

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

No annotations are provided, so the description bears the full burden. It does not disclose the default calendar scope (all calendars vs. one), sorting order, or behavior when calendar_name is invalid. The phrase 'upcoming' implies a time filter but lacks specifics like timezone handling or recurrence expansion.

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 extremely concise: one lead sentence and a clean Arg list. Every word earns its place, with no fluff or repetition. It is well-structured and front-loaded.

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?

Despite having an output schema that likely covers return values, the description lacks essential behavioral details for a listing tool, such as whether events from all calendars are included when calendar_name is omitted, or if the default is a specific calendar. The tool's interaction with siblings (list_calendars, create_calendar_event) is not clarified, leaving a sense of incompleteness.

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 the parameters. The Args section does add meaning: days_ahead is described as 'Number of days to look ahead' with a default, and calendar_name as 'Optional specific calendar name.' This adds value, but it omits edge cases (e.g., negative days, invalid calendar names) and does not reference list_calendars for valid names.

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 the tool's function with a specific verb and resource: 'List upcoming calendar events.' It is distinct from siblings like list_calendars (which lists calendars) but does not explicitly reference alternatives, so it slightly misses the top score.

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?

There is no guidance on when to use this tool versus alternatives such as list_calendars or create_calendar_event, nor any exclusions. The description merely explains what it does without context for selection.

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