create_calendar_event

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

With no annotations provided, the description shoulders the behavioral disclosure burden. It reveals the crucial DTEND exclusivity behavior and notes that participants automatically adds ORGANIZER from CalDAV username. This goes beyond typical descriptions, though it omits potential side effects like permission requirements.

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 core purpose, and every sentence adds unique information. It wastes no words.

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?

Given the 7 parameters and no output schema, the description covers the most important behavioral nuances (DTEND exclusivity and automatic ORGANIZER). It does not explain return values or error conditions, but the schema already documents all parameters well. For a creation tool, this is reasonably complete.

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?

Despite 100% schema description coverage, the description adds value by providing a concrete example of the DTEND exclusion (a one-day event on April 1 needs end: 2026-04-02) and clarifying the date-only format for all-day events. This helps agents understand parameter semantics beyond the schema.

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 it creates a new calendar event, specifies support for date-only format for all-day events, and explains the DTEND exclusivity per RFC 5545. This distinguishes it from sibling tools like update_calendar_event or list_calendar_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 explicit guidance on when to use date-only format and how to set DTEND correctly for all-day events. It does not explicitly state when not to use this tool or suggest alternatives, but the context of a creation tool is clear.

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