list_calendar_events

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

With no annotations, the description carries the whole burden. It does contribute one real behavioral constraint (web mode only) and the verb "lists" implies a non-mutating read, but it says nothing about the time window returned, pagination, or ordering, which matters for an events listing.

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?

Two short sentences, purpose first, constraint second, with no filler. Every clause carries information.

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 parameterless read tool with no output schema and no annotations, the definition is roughly adequate but leaves open what event set is returned (all connected calendars? what date range?) and what the results look like. A brief note on scope or the default range would close the main gap.

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 tool takes zero parameters, so there is nothing for the schema to describe and no semantic gap for the description to fill; baseline 4 applies. The description does not invent parameter behavior that does not exist.

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?

States a specific verb+resource: "Lists events bound from connected calendars." It is distinguishable from siblings like list_calendar_accounts and list_calendar_subscriptions by returning events rather than accounts/subscriptions, though it never names those siblings explicitly.

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?

"Web mode only" tells the agent where the tool is available, but not when to choose it over list_calendar_accounts or list_calendar_subscriptions, nor what prerequisites (e.g., a connected calendar) must hold. No alternatives or exclusions are given.

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