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

The annotations already declare destructiveHint=true, so "Destructive." is largely a restatement, though it reinforces severity. The genuinely additive part is "from a real connected calendar," which tells the agent this mutates an external provider's state rather than a sandbox copy. It still omits whether the delete is idempotent, what happens for an unknown event_id, and whether specific OAuth scopes are required.

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 tight sentences: the operation and its target come first, severity second, and the REST mapping last. Nothing is padded and the ordering is front-loaded.

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 two-parameter destructive call with no output schema, the description plus annotations cover the essentials. It stops short of describing failure modes, idempotency, or permission requirements, which leaves clear gaps for a real-calendar mutation.

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% and both parameters are documented there, including the note that event_id is sent in the JSON body. The description's "by your event_id" adds emphasis but no new semantics, so the baseline 3 applies.

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?

States a specific verb and resource ("Deletes an event") and scopes it to "a real connected calendar," which separates it from purely local bookkeeping. It does not explicitly differentiate itself from the sibling cronofy_upsert_event, which is the natural alternative for modifying calendar state.

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?

There is no when-to-use or when-not-to-use guidance and no mention of alternatives such as cronofy_upsert_event. The use case is inferable from the name, but the description itself provides no routing help.

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