Create Calendar Event

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

The description provides no behavioral details beyond the action itself. The annotation destructiveHint: true suggests the operation may have destructive side effects, but the description doesn't clarify what those are (e.g., overriding existing events, requiring specific permissions). It doesn't mention that it creates a permanent record or any side effects like notifications.

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?

Single sentence, no fluff. It's appropriately concise for a simple create operation.

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 create operation, the description is minimal. It doesn't specify what the response will be (e.g., the created event object), which is important for the agent to process the result. Since there's no output schema, the description should at least mention the return type. It also doesn't mention any validation or error conditions.

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 baseline is 3. The description adds no extra meaning beyond the schema, such as explaining the relationship between start_at and end_at or the format of context_code. It doesn't compensate for any ambiguity in 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 states a clear verb ('Create') and resource ('new calendar event') and explicitly scopes to Canvas. It distinguishes from sibling tools like list_calendar_events and update_calendar_event by the verb 'create'. However, it doesn't specify whether this creates events in course, user, or group calendars, which could be ambiguous.

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?

No guidance on when to use this vs alternatives. It doesn't mention that update_calendar_event exists for modifications or list_calendar_events for querying. No context on prerequisites like permissions or whether the context_code must exist.

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