next_occurrences

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

With no annotations, the description carries the burden and does disclose meaningful behavior: modified instances and removed dates are applied, and `after` defaults to now. It does not state error behavior for unknown UIDs or how timezone conversion interacts with the results, which keeps it short of a 5.

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?

Three tight sentences, front-loaded with the core behavior, then the use case, then the disambiguation note. No filler and nothing repeated from the schema.

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 need not be explained, and the description covers the recurrence-expansion semantics and UID sourcing well. The only real gap is the unexplained `tz` parameter, which matters for a date-producing tool.

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 0%, so the description must compensate, and it does for most parameters: n (the count), after (default now), calendar (file name, only needed when the UID exists in several files), and event_uid (sourced from agenda/search_events). The `tz` parameter is never mentioned, leaving one of five undocumented.

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 and resource: the next n occurrences of one event identified by UID, at or after a given point. It also distinguishes itself from the sibling list tools (agenda, search_events) by being the recurrence-expansion tool rather than a listing tool.

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?

Gives a clear use case ('check what a recurrence rule really produces, e.g. last Friday of the month') and tells the agent where UIDs come from (agenda and search_events). It lacks an explicit when-not or a named alternative for the case where the agent just wants a plain listing, but the context is otherwise unambiguous.

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