calendar_create_event

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

With no annotations, the description must carry the burden. It states the core behavior (creating an event) and adds that add_google_meet auto-generates a Meet link. However, it omits other behavioral aspects like permissions, invite side effects, or return value expectations.

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?

Two sentences, front-loaded with the action, and every sentence provides useful details. No fluff or redundancy.

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 9-parameter tool with 3 required params and zero schema descriptions, this description is inadequate. It covers only datetime and Meet link behavior, leaving most parameters undocumented. The output schema exists, so returns needn't be described, but parameter coverage is too sparse.

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 0%, so the description must compensate. It clarifies start/end formats (RFC3339 vs YYYY-MM-DD) and the add_google_meet flag, but leaves summary, location, timezone, attendees, calendar_id, and description unexplained. Only 2 of 9 parameters receive added meaning.

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 'Create a calendar event', which is a specific verb and resource. It distinguishes from update/delete but not from the similar sibling calendar_quick_add, which also creates events.

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?

No guidance is provided on when to use this tool versus alternatives like calendar_quick_add or calendar_update_event. The description only gives parameter formatting instructions, not context for tool selection.

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