get_upcoming_calendar_events

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

With no annotations provided, the description carries the full burden. It conveys read-only behavior ('Retrieves') and a key behavioral trait (aggregating across all active Google Calendars) and time scoping ('within next X days'). However, it does not clarify edge cases like event filtering or the meaning of 'active', leaving some ambiguity.

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 a single concise sentence that efficiently communicates the core purpose. No filler or redundant wording, and it front-loads the key verb and resource.

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 tool is a simple read operation with only two optional parameters and an output schema. The description covers the primary behavior (retrieving events) and scope (all active calendars, time range). Minor gaps remain around parameter usage and 'active' semantics, but overall it is adequate given the tool's simplicity and presence of an output schema.

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 indirectly references days_ahead via 'next X days' but does not mention max_results or defaults, nor how these parameters control output. The agent must infer from parameter names alone, which is insufficient.

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 retrieves upcoming events across all active Google Calendars within a specified time frame. It uses a specific verb ('Retrieves') and resource ('upcoming events across all active Google Calendars'), distinguishing it from calendar mutation tools like add_calendar_event and delete_calendar_event.

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 description implies the tool is used for reading upcoming events but offers no explicit when-to-use/when-not-to-use guidance or mentions of alternative tools. It does provide context that it aggregates across all active calendars, but lacks direct exclusions or comparisons to siblings.

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