Create Calendar Event

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

Beyond the annotations, the description discloses that the event is saved immediately with no draft or publish step, that duplicates are created on repeat calls, and that creating in the target context requires permission. These are meaningful behavioral details for a mutation tool, and they are consistent with the mutation-oriented annotation profile.

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 front-loaded with the core action and return value, then adds only decision-relevant details about context targeting, duplicate behavior, update alternatives, persistence, and permissions. Despite its length, each sentence carries useful information for correct invocation.

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?

There is no output schema, but the description names the key returned fields (`id`, `start_at`, `end_at`, `workflow_state`). It also covers permissions, duplicate behavior, persistence, and the relationship to sibling tools, leaving no important operational gap for this create operation.

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 100%, so the schema already explains all six parameters. The description adds meaningful semantic clarification for `context_code`, noting that it can target a course, group, user, or account context rather than only courses, which goes beyond the schema's course-shaped example.

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 states a specific verb and resource ('Create a new calendar event') and explicitly says it returns the created event object with named fields. It also distinguishes creation from updating and from listing existing events, so an agent can select it confidently.

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?

It explicitly says to check `list_calendar_events` first and to use `update_calendar_event` with the returned `id` when changing an existing event. It also warns that repeating the same create call produces a duplicate rather than an update, which gives clear when-to-use and when-not-to-use guidance.

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