calendar_delete_event

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

Discloses that the tool attempts the call and may report 'not_implemented' if unavailable, adding important behavioral context beyond the basic action. No annotations present, so description carries full burden.

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?

Two concise sentences: first states purpose, second adds critical caveat. No filler, front-loaded and efficient.

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?

Covers core action and important limitation. Output schema exists but not described; for a simple delete tool, this is largely adequate. Minor omission: no mention of what happens on successful deletion.

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?

Description explains that `uid` identifies the event, but does not clarify the role of `entity_id`. With 0% schema coverage, more parameter detail would be beneficial. Only one of two required parameters is explained.

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 'Delete a calendar event by its `uid`', using a specific verb and resource. It distinguishes from sibling tools like calendar_create_event and calendar_list_events.

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?

Implies usage for deleting events, and adds caveat about HA not exposing a stable service, which helps set expectations. However, lacks explicit when-to-use vs alternatives.

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