get_calendar_events

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

No annotations are present, so the description carries full responsibility. It only states 'Get upcoming calendar events' without revealing any behavioral traits (e.g., read-only, pagination, time range defaults, or required scopes). For a tool that may retrieve many events, this is insufficient.

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 sentence, which is concise and avoids verbosity. However, it sacrifices crucial details for brevity. It earns points for efficiency but loses some for under-specification.

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?

Given the tool's simplicity (one optional parameter, no output schema, no annotations), the description is too brief. It omits context such as which calendar is targeted, whether it returns all day events, or how it handles recurrence. The presence of many sibling calendar tools amplifies the need for completeness.

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 coverage is 100% for the single parameter 'days', which the schema already describes as 'Number of days ahead to look (default: 7)'. The description adds no new semantic meaning beyond the schema, so it scores at the baseline of 3.

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 'Get upcoming calendar events' specifies a verb and resource, but it is vague. It does not clarify which calendar (e.g., primary, all), and it fails to distinguish from sibling tools like get_calendar_view or get_event_details, which also deal with calendar events.

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?

No guidance is provided on when to use this tool versus alternatives such as get_calendar_view or find_meeting_times. There is no mention of exclusions or context for appropriate use.

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