Delete Event

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds real value by disclosing that the call changes community state and is gated behind confirm=true, but it omits consequences (what happens to attendees, whether deletion is reversible) and any permission requirements.

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 short sentences, with the action and the confirm requirement front-loaded and no wasted prose. The first sentence merely restates the name/title, which is the one redundant element.

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?

For a destructive, non-idempotent mutation with four parameters and no output schema, the description covers the confirm gate but says nothing about side effects on related records, permissions, or error conditions. It is adequate given the annotations, but not complete.

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% and the schema itself explains confirm and account well, so the description does not need to document parameters. Its only parameter-related content (confirm=true) duplicates the schema, adding no new syntax or edge-case meaning.

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 states a specific verb and resource ("Delete Event") that clearly separates it from siblings such as delete_event_attendee, update_event, and duplicate_event. It is essentially the title restated plus one behavioral clause, so it is clear but not distinctive in wording.

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?

It implies usage through the confirm=true gate ("for the user-requested action"), which tells the agent this is a deliberate, user-initiated action. However, it never says when to delete versus archive/update an event or how this differs from delete_event_attendee, so alternatives are left to inference.

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