Get calendar event

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

With no annotations, the description carries the behavioral disclosure burden. 'Fetch' signals a read-only operation, and the description goes further by explaining exactly what a repeating event returns: first occurrence, recurrence rule, excluded occurrences, and modified occurrences. This is valuable context beyond the schema.

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 two tightly written sentences. The action is front-loaded, and the second sentence adds high-value recurrence behavior without any 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?

This is a simple read tool and an output schema exists, so return values are covered. The recurrence behavior is a strong addition. However, the under-explained required calendar_name parameter leaves a meaningful gap in the input contract, making the description incomplete for fully 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 description coverage is 0%, so the description must explain the parameters. It addresses event_id but completely omits calendar_name, which is required and has no documented meaning. An agent cannot tell why calendar_name is needed or how it relates to event_id from this description.

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 uses a specific verb and resource ('Fetch one event by its event_id') and clearly distinguishes this from list_events by emphasizing it returns a single event. The added detail about repeating events gives additional precision and makes the tool's scope 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 description clearly implies this tool is for retrieving a single known event by ID, which is a clear usage context. It does not explicitly contrast with list_events or state when not to use it, but the one-by-ID framing is enough for an agent to route correctly most of the time.

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