calendar_event_create

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

No annotations are provided, so the description carries the full burden. It discloses the need for alias credentials but does not mention other behavioral traits such as expected return value, validation, or side effects. The write nature of the operation is only implied by the verb 'create'.

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 concise with a single sentence that communicates the core purpose and a key prerequisite. It is appropriately sized for a create operation, though it could have used an extra sentence for guidance or return value.

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?

The tool has no output schema, so the description should explain the return value or success criteria, but it does not. It also lacks context about CalDAV-specific behavior or the relationship to calendars_list/calendar_get. The description is minimal and leaves the agent to infer too much.

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 100%, so the parameters are already well-documented. The description adds no additional parameter-level context, but the baseline of 3 is appropriate since the schema does the heavy lifting.

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 uses a specific verb and resource ('Create a calendar event') and distinguishes from sibling tools like calendar_event_update and calendar_event_delete. The mention of 'for an alias (CalDAV)' clarifies the target context.

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 a new calendar event and explicitly states a prerequisite ('Requires alias credentials'). However, it does not provide explicit alternatives or exclusionary guidance, such as pointing to calendar_event_update for existing events.

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