calmesh_create_event

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

With no annotations, the description carries the full burden. It discloses the mutation (creates an event), the requirement for 'write' scope or higher, and the default source selection behavior. It could mention potential failure modes, but the key side effects and prerequisites are covered.

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 three sentences, front-loaded with the action, and each sentence contributes: purpose, default target behavior, and prerequisite/scope. There is no wasted text.

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 8 parameters, 100% schema coverage, and no output schema, the description provides essential non-schema information: default target, slug lookup, and required scope. It does not explicitly cover the return value, but that is not mandatory without an output schema, and the description suffices for safe invocation.

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?

All parameters have schema descriptions, so the baseline is 3. The description adds value by explaining the default source_id behavior and directing users to list_calendars for slugs, enriching the semantics of these parameters beyond their schema text.

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 calendar event on a connected calendar, using a specific verb and resource. It distinguishes itself from sibling tools like calmesh_create_booking and calmesh_create_poll by specifying 'calendar event' and explaining the default write target behavior.

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 clear context by directing users to calmesh_list_calendars for finding slugs and explains the default write target logic. However, it does not explicitly mention alternatives or when not to use this tool, so it lacks full exclusionary guidance.

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