calendar_events

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

No annotations provided; description lacks behavioral details such as pagination, rate limits, authorization, or handling of recurring events. Only mentions ISO date format. Inadequate for a listing tool without annotation safety net.

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?

Single sentence efficiently conveys core purpose and key details. No filler or redundancy.

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 output schema exists, description covers main behavior: date range, account scope, calendar default. Could mention sorting, limits, or filtering, but not essential for basic use.

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 0%; description adds minimal meaning: only clarifies that calendar_id defaults to primary and that dates are ISO format. Other parameters (account, start, end) are not elaborated beyond their names and schema defaults.

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?

Description clearly states 'List events' with specifics: between two ISO dates/datetimes, across one or all accounts, and calendar_id defaults to primary. Distinguishes from siblings like calendar_create_event (create) and calendar_list (list calendars).

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?

Implies usage for listing events but provides no explicit guidance on when to use vs alternatives, nor when not to use. Sibling names suggest distinct purposes but no explicit context.

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