Create Calendar Event

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

The description says 'create' which is additive, but annotations declare destructiveHint: true, suggesting the tool may have destructive effects. This is a direct contradiction. The description adds no further behavioral context beyond this conflict.

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?

One sentence, front-loaded with the verb and resource. No wasted 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?

While the schema covers parameters fully, the description lacks any context about side effects or return behavior, and the destructiveHint contradiction creates confusion. For a simple create operation, a one-liner could suffice, but the annotation conflict makes it incomplete.

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?

All 6 parameters have descriptions in the schema, so the description does not need to compensate. The description adds no additional parameter semantics beyond the schema's full coverage.

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), the resource (calendar event), and the platform (Canvas). It distinguishes from sibling tools like update_calendar_event and list_calendar_events by specifying 'new'.

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 no guidance on when to use this tool versus alternatives like update_calendar_event or list_calendar_events, nor any exclusions or prerequisites.

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