calendar_createEvent

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

The description mentions two features (Google Meet and Drive attachments) but does not disclose behavioral details such as default calendar, notification behavior, or that attachments replace existing ones. Since no annotations are provided, the description carries the burden of behavioral disclosure, and it falls short.

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 a single, front-loaded sentence with no redundant words. It efficiently communicates the core action and key features, earning high marks for structure.

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?

Given the tool's complexity (9 parameters, nested objects, no output schema), this two-line description is insufficient. It does not mention return values, defaults for calendarId or sendUpdates, or any prerequisites, leaving the agent to discover these from the schema.

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 covers 78% of parameters with descriptions. The tool description adds relevance for addGoogleMeet and attachments, but does not explain start/end format or sendUpdates default, which are already in schema. It provides modest added meaning beyond the schema.

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 the tool creates a new calendar event, using a specific verb and resource. It also mentions support for Google Meet and Drive attachments, which distinguishes it from related tools like update or delete.

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 implies usage for creating new events but does not explicitly contrast with sibling tools like calendar_updateEvent or calendar_deleteEvent. No when-to-use or exclusions are provided, leaving the agent to infer from the verb.

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