calendar_events

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

Without annotations, the description bears full burden. It discloses that events have fields like `is_meeting` and `attendees`, and advises on classification, but does not explain sorting, pagination, permissions, or output structure beyond the bare mention of time/participants/host.

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 short (two sentences) and front-loaded with the core purpose. However, the second sentence is somewhat cryptic and could be clearer. Overall, it is concise with minimal waste.

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?

An output schema exists, so return values are partially covered. The description mentions important fields but omits filter behavior (date range, user scope) and does not explain the absence of user_id parameter documentation. The interpretation advice adds value but leaves gaps.

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 67% (days and start have descriptions, user_id does not). The description adds no parameter-specific details, leaving user_id undocumented and failing to explain how days and start affect the query.

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 the tool provides calendar events with time, participants, and host, which clearly indicates retrieval of event details. However, it lacks an explicit verb like 'list' or 'get', and the description veers into interpretation advice rather than a straightforward purpose statement.

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 offers no guidance on when to use this tool versus alternatives, nor does it specify prerequisites or filtering scope. It only gives interpretation advice for event data, not usage context.

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