calmesh_delete_event

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It mentions the 'write' scope requirement, but omits critical behavioral traits such as whether deletion is permanent, irreversible, or affects related data. It also does not describe error behavior or side effects. For a delete operation, these are essential gaps.

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 exceptionally concise—two sentences front-loaded with the core action. Every sentence serves a purpose: defining the operation and explaining what IDs are needed and the scope requirement. No redundant or extraneous 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?

The tool has 3 parameters, no output schema, and no annotations. The description explains purpose, ID provenance, and scope, but omits the required 'slug' parameter entirely. It also does not mention return values or error handling, which matters since no output schema exists. These omissions make the description incomplete for a delete operation.

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 baseline is 3. The description adds value by noting that remote_event_id can come from calmesh_get_events in addition to calmesh_create_event, and clarifies source_id's role. However, it fails to mention the required 'slug' parameter, listing only remoteEventId and sourceId as requirements, which could confuse an agent about required inputs.

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 action: 'Delete a calendar event from a connected calendar.' The verb 'Delete' and resource 'calendar event' are specific, and the tool is clearly distinct from siblings like calmesh_create_event or calmesh_get_events. The purpose is unambiguous.

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 usage context: it requires the remoteEventId (from calmesh_create_event or calmesh_get_events) and the sourceId identifying the calendar source. It also notes the 'write' scope requirement. However, it does not explicitly mention alternatives or when-not-to-use scenarios, but the context is sufficient for selecting the tool.

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