find_calendar_events

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

With no annotations, the description carries the full burden and does disclose two meaningful behaviors: the default 30-day window and that recurring events are expanded into individual occurrences (which affects result volume). It is silent on result ordering, pagination behavior, whether all calendars are searched when none is specified, and any permission requirements.

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 tight sentences, no filler, and the core scope plus default behavior are front-loaded before the recurrence note.

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 5-parameter read tool with no annotations, no output schema, and 40% schema coverage, the description is adequate but leaves real gaps: which calendar is searched by default, how results are ordered, and whether limit truncates occurrences or base events. These matter for correct invocation.

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 only 40%, and the description compensates for part of it by explaining that text is an optional match filter and that the two time bounds define the search window (with a default). It says nothing about the 'calendar' parameter's semantics (default calendar vs. all calendars) or how 'limit' interacts with recurrence expansion, leaving two of five parameters unexplained in prose.

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 (find) and resource (calendar events) plus the temporal scope, which implicitly separates it from the create/update/list_calendars siblings. It never explicitly contrasts itself with those siblings, but the read/search nature is unmistakable.

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 default window ('the next 30 days') and the optional text filter imply the intended use case, but there is no explicit when-to-use or when-not-to-use guidance and no pointer to a sibling for other needs (e.g., listing calendars first to obtain a calendar identifier).

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