calendar_create_event

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

Discloses invitation behavior (Google sends real invites). No annotations exist, so description carries burden. Missing details on other behaviors (e.g., date format, defaults).

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?

Single sentence with front-loaded action. Concise but could be slightly more structured. No wasted words.

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?

Lacks detail on required parameters (datetime format, account selection), no output schema info. Incomplete for a 9-parameter tool with no annotations.

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?

With 0% schema description coverage, description only clarifies 'attendees' and 'send_invites' via 'optionally inviting'. No explanation for 7 other parameters (account, start, etc.).

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?

Clear verb 'Create' and resource 'event'. Distinguishes from sibling tools like calendar_events (read) and calendar_list (list calendars) by being the only creation tool.

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?

Explicitly warns about real invitations, advising user confirmation. Provides context-sensitive guidance, though lacks explicit alternative conditions.

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