create_calendar_event

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

No annotations are provided, so the description carries full burden. It discloses cost (~5⚡ for LLM extraction), backend behavior (linked Apple Calendar, Google Calendar, or ics file), timezone fallback chain, and return format. No contradictions.

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 detailed and structured, but slightly verbose. It could be more concise while retaining key information, but overall it is well-organized with clear sections.

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 complexity of the tool (multiple backends, timezone handling, cost), the description covers all necessary aspects comprehensively. It explains the return value in detail, compensating for the absence of an output 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?

Schema coverage is 100%, and the description adds significant value beyond the schema: it explains the timezone parameter's usage ('ALWAYS pass timezone=IANA when you know it') and provides examples and limitations (recurring not supported) for the description parameter.

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's purpose: 'Schedule a calendar event from a natural-language description'. The verb 'schedule' and resource 'calendar event' are specific, and the description distinguishes it from sibling tools (e.g., create_avatar, generate_image) by focusing on calendar scheduling.

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 explicit guidance on when to use: when the user provides a natural-language description to schedule an event. It explains timezone handling and when to pass timezone. However, it does not explicitly state when not to use the tool or mention alternatives.

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