create-calendar-event

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so description only needs to add context. It mentions creation but fails to disclose potential side effects like sending invitations or online meeting initialization behavior, which are important for an agent.

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?

Description is three sentences with no redundant information. First sentence clearly states purpose and capabilities; second sentence is a well-emphasized tip. Efficient and front-loaded.

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 description covers main features and includes a useful tip, it lacks details about the return value (the created event object) and important behavioral contexts such as invitation sending or online meeting details. Given the complexity of nested objects and no output schema, this is a notable gap.

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 high (67%), so baseline is 3. The description adds a tip about using list-users for attendee emails, which provides parameter-specific guidance beyond the schema. Also briefly lists key parameters, aiding understanding.

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?

Description clearly states it creates a new calendar event on the user's calendar and lists supported features (subject, time, attendees, etc.). However, it does not explicitly differentiate from sibling 'create-specific-calendar-event', which might create events in a specific calendar.

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?

Description provides a critical tip to use list-users tool for email addresses instead of guessing, which is explicit usage guidance. However, it does not specify when not to use this tool or mention alternatives like 'create-specific-calendar-event'.

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