apple_calendar_create_event

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

The annotations indicate a non-read-only, non-idempotent write operation. The description adds context by specifying 'new' (create vs. update) and 'local' (calendar scope), which goes beyond the annotations. However, it does not disclose permissions, side effects, or duplicate behavior.

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 concise sentence with no fluff, front-loaded with the verb and object. It is appropriately sized for the purpose clarity it provides.

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?

With 7 parameters, low schema coverage, and no output schema, the description is insufficient. It doesn't explain parameter values, behavior on local calendars, or how to use the tool in context. It's a minimal one-liner.

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 very low (only 'calendar' has a description). The tool description adds no parameter information, leaving date format, allDay semantics, and required parameters unexplained. This is a significant gap for a tool with 7 parameters.

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 action ('Create') and the object ('a new local Calendar.app event'), distinguishing it from sibling tools like apple_calendar_update_event and apple_calendar_delete_event. The 'local' qualifier adds specificity.

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 does not provide any guidance on when to use this tool versus alternatives like apple_calendar_update_event, nor does it mention prerequisites such as available calendars or required date formats. It only implies usage by its name and description.

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