calendar_create_event

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

With no annotations, the description carries the burden of disclosing behavior. It reveals that including attendees sends calendar invitations and requires confirm: true as a safety gate, which is a key side effect beyond the tool's name. While it doesn't cover every possible behavior, the most critical risk is disclosed.

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 two concise sentences, with the main purpose in the first and the critical safety condition in the second. It is front-loaded, has no unnecessary words, and every sentence adds value.

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?

For a create operation with 11 parameters and no output schema, the description covers the most important behavioral context (the confirm/attendees safety gate) while relying on the schema for parameter details. It is complete enough for an agent to avoid the main pitfall, though it could optionally mention auth or return values.

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 schema already documents all 11 parameters with 100% coverage, providing a baseline of 3. The description adds meaningful semantic value by explaining the cross-parameter constraint that attendees require confirm: true, which isn't evident from individual parameter descriptions. This elevates the score.

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 states 'Create a new Google Calendar event' with a specific verb and resource, clearly distinguishing it from sibling tools like calendar_update_event, calendar_list_events, and calendar_delete_event. The added detail about confirm for attendees further clarifies the action's 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 provides clear context for when to use the tool (creating new events) and explicitly states the condition under which confirm must be true (when attendees are included). However, it does not explicitly mention alternatives or when not to use this tool, so the guidance is clear but lacks explicit exclusions.

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