create-calendar-event

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

Annotations indicate destructiveHint=true, consistent with creation, but the description only mentions creating extended properties, not the actual creation of a calendar event. This lack of clarity about the tool's primary function misleads the agent about its behavioral traits.

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 poorly structured with incomplete sentences like 'The following user resources are supported: The following group resources are supported:' and lacks conciseness. It includes a tip but fails to communicate the core functionality efficiently.

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 complexity of the tool (nested objects, many parameters, no output schema), the description is woefully incomplete. It does not explain that the tool creates a calendar event or provide necessary context for the extensive parameter schema.

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?

The input schema provides descriptions for includeHeaders and excludeResponse (67% coverage), and the body parameter is described in its nested structure. The description adds no additional meaning beyond the schema, so it meets the baseline for moderate 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 tool name 'create-calendar-event' suggests creating a calendar event, but the description focuses on creating multi-value extended properties, which is contradictory and misleading. The description does not clearly state that it creates a calendar event.

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?

There is no guidance on when to use this tool versus alternatives like 'create-specific-calendar-event' or 'update-calendar-event'. The tip about using list-users for email addresses is helpful but not about tool selection.

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