Create Event

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

With no annotations provided, the description carries the burden of behavioral disclosure. It adds useful context about accepted date/time formats and calendar selection, but it does not mention permissions, default handling of missing fields, mutation effects, or what the response contains.

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 sentences long, front-loaded with the primary action, and contains no filler. The first sentence states what the tool does and the second clarifies the important date/time input flexibility.

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 9-parameter creation tool with no annotations and no output schema, this description is too thin. It lacks details on how optional fields interact, how calendarId selection works, what happens when allDay is set, and what a successful response contains.

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 22%, and the description mostly repeats the start/end format guidance already present in the property descriptions. It does not explain the roles of calendarId, allDay, timeZone, location, notes, or url, leaving the agent without enough parameter-level guidance for constructing valid calls.

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 opens with the specific verb 'Create a calendar event' and clearly identifies the resource, distinguishing this tool from sibling tools like calendar_update_event and calendar_delete_event. It also notes the option of using the default or a specified calendar, adding useful scope.

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 makes it clear when to call this tool: to create a calendar event. It provides useful context about the default versus a specified calendar. However, it does not explicitly mention alternatives or state when not to use it (e.g., use update for existing events).

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