create-calendar-event

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the description's mention of 'create' is consistent and adds little beyond the listed features (online meetings, recurrence). No contradictory information is present.

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 concise: two sentences plus a tip, no wasted words. The most important information (what the tool does) is front-loaded. The tip is emphasized but remains efficient.

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?

The tool has a complex input schema with many optional fields and no output schema. The description covers core features and a critical tip, but does not mention what the tool returns (presumably the created event) or any other contextual notes like behavior with online meetings.

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 high (75%) description coverage, so the description does not need to detail each parameter. It summarizes the key adjustable fields (subject, times, etc.) and adds the email tip, which is more of a usage guideline. 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 creates a new calendar event on the user's default calendar, listing the main settable attributes (subject, times, location, attendees, etc.). This distinguishes it from sibling tools like create-specific-calendar-event (which targets a specific calendar) and update-calendar-event (which modifies existing 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 includes a critical tip to use list-users to find recipient email addresses, but does not explain when to use this tool versus create-specific-calendar-event or other alternatives. There is no guidance on prerequisites or exclusions.

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