list_upcoming_events

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It indicates a read-only listing operation, but it does not disclose what 'upcoming' means, how many events are returned, the default limit, ordering, or whether the user's default calendar can be changed.

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, front-loaded sentence with no filler words. It communicates the core operation efficiently, which is exactly what conciseness calls for.

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 tool with no output schema, no annotations, and a parameter that is undocumented in the description, the definition is too thin. It does not explain the meaning of the 'top' parameter, the time window for 'upcoming', or how the result set is ordered, leaving important gaps for an agent.

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?

The schema has one parameter ('top') with 0% description coverage, and the tool description does not mention it at all. The agent receives no explanation of what 'top' controls, despite the schema showing a default of 20.

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 states a specific verb ('List'), a specific resource ('upcoming events'), and a clear scope ('the user's default calendar'). This distinguishes it from sibling tools like list_events_in_range, get_event, and list_calendars without needing to open the schema.

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 about when to use this tool versus alternatives such as list_events_in_range or list_event_instances. The description simply states what it does without any exclusion conditions or routing hints.

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