calendar_create_event

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

The description says 'Create' which is a non-destructive action, but the annotations set destructiveHint=true. This is a direct contradiction; the description does not disclose any destructive behavior, making the annotation misleading.

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 brief and focused, conveying the essential purpose and key constraints without unnecessary detail. It uses clear, direct language.

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 and the description does not mention what the tool returns (e.g., the created event). It also omits potential side effects or error conditions, leaving the agent without complete operational context.

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 only 25% (only calendarId has a description). The description provides some context about time zones and recurrence but does not explain most parameters (accountId, requestId, or the many nested event fields), leaving the agent to infer from names alone.

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 that the tool creates an appointment or invitation, and it distinguishes itself from sibling tools like calendar_update_event and calendar_delete_event. The mention of constraints like 'No online meeting creation' further clarifies its 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 for creating calendar events and includes specific constraints (explicit Windows-zone local times, bounded recurrence, WebAuthn review exceptions). However, it does not explicitly state when to prefer this tool over alternatives, though the create action is fairly evident.

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