create_calendar_event

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

Annotations already declare destructiveHint=true and non-idempotency, and the description adds critical behavioral context: the operation is irreversible after dry_run=False, only personal events are supported, and explicit user confirmation is required before the real write.

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?

Four short sentences, front-loaded with purpose and risk, followed by scope and workflow. Every sentence adds operational value with no repetition.

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?

Complete for a destructive create tool: it covers purpose, irreversibility, scope limits, and the required dry-run confirmation flow. The output schema exists, so the description need not explain 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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaningful dry_run policy beyond the schema: preview first, show the user, and only create after explicit confirmation. It does not add extra syntax or constraints for timestart/duration beyond what the schema documents.

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?

States a specific verb and resource ("Create a personal calendar entry") and immediately scopes it to personal/user events, excluding course/group events. An agent can tell this is a creation tool for personal calendar entries, distinct from listing or deleting 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?

Gives clear usage context and an explicit safety workflow: call with dry_run=True first, show the preview, then call again with dry_run=False only after confirmation. It also states the when-not case (course/group events are unsupported), though it does not name sibling alternatives.

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