create-specific-calendar-event

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

Annotations already indicate destructive and not read-only. The description adds no additional behavioral context, such as permissions required, irreversible changes, or side effects. The tip hints at a common pitfall but doesn't clarify behavior.

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 short with two sentences and a tip. It is front-loaded with purpose and includes a critical tip. No redundant information.

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?

The description lacks details about return values (no output schema mentioned), required fields, and error scenarios. For a creation tool with nested objects, more context about what is returned would be beneficial.

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 75%, so the schema already documents most parameters. The description does not elaborate on any parameters beyond what's in the schema. The tip indirectly relates to the 'attendees' sub-property of 'body' but doesn't explain it directly. Baseline 3 is appropriate.

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 it creates a new event in a calendar, specifying user or group calendars. However, it does not distinguish itself from sibling 'create-calendar-event', which might have different behavior. The verb and resource are clear.

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 tip instructs not to guess email addresses and to use list-users, which is helpful. However, there is no guidance on when to use this tool versus alternatives like 'create-calendar-event', nor any exclusion criteria.

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