Create Calendar Event

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

Annotations already indicate readOnlyHint false, destructiveHint false, and idempotentHint false, so the agent knows it's a non-destructive write. The description adds valuable behavioral context: with no attendees, it becomes a private appointment and nothing is sent. This goes beyond annotations and clarifies the invitation behavior.

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?

Two sentences, front-loaded with the core action, and no filler. Every word earns its place. The second sentence adds crucial behavioral nuance without bloating the description.

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 14 parameters, full schema descriptions, and an output schema, the description need not re-explain return values or parameter details. It covers the essential high-level behavior (creation, recurrence, attendee invites, privacy). Slightly more context about when recurrence or attendees are used could help, but the schema and annotations fill that gap adequately.

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 100%, so the baseline is 3. The overall description does not add parameter-specific meaning beyond what the schema already provides; it only mentions invite attendees, which is also captured in the attendees parameter description. No additional semantic value is added.

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 action ('Create a calendar event'), the resource (calendar event), and key distinctions (one-off or recurring, invite attendees). It is easily distinguishable from sibling tools like get_calendar_events, update_event, and cancel_event by its explicit create verb and 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 implies usage context (creating events) but does not explicitly state when to use this tool over alternatives or provide exclusions. The note about no attendees affecting privacy is a usage condition, but no alternative tools are mentioned. It is adequate but not explicit.

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