Create Event

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

The description simply restates the action without disclosing behavioral traits beyond the annotations. Annotations already indicate readOnlyHint false and non-idempotent, but the description does not add context such as duplicate event creation on repeated calls or calendar-specific behavior. No contradiction with annotations.

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 a single, clear sentence with no superfluous words. It is efficiently structured and front-loaded, though it omits additional helpful details.

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?

With 7 parameters, 3 required, and no output schema, the one-sentence description is insufficient. It does not explain what the function returns, how calendars are selected (e.g., calendarUrl vs calendarName), or any side effects. The schema covers parameters but the overall context for using the tool is minimal.

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 input schema has 100% parameter description coverage, so the schema fully documents each parameter. The description adds no additional parameter semantics beyond what the schema provides, so a baseline score of 3 is appropriate.

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 clearly states the tool's function—creating a new calendar event—using a specific verb and resource. This distinguishes it from sibling tools like update-event, delete-event, and list-events.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites such as calendar selection or authentication. It is implied by the name, but no explicit context 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.