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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuinely non-redundant behavior: stored events are retained while new events of the type are rejected — this is the key operational fact beyond what annotations say. It stops short of stating what happens to in-flight or referenced events, or error behavior for an unknown ID.

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, zero filler, with the action front-loaded and the non-obvious side effect immediately after. Nothing could be cut without losing information.

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 single-parameter delete with full annotation coverage and no output schema, this is nearly complete: the agent knows the action, the identifier, and that stored data survives. A brief note on whether deletion is reversible or fails on unknown IDs would close the remaining gap.

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?

Only one parameter and schema coverage is 100%, with the schema itself documenting the accepted 'etp_xxx / name / w:name' forms. The description adds no parameter-level meaning, 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 ('Delete') plus a precisely scoped resource ('a workspace event definition'), and the second sentence disambiguates it from deleting the stored events themselves — a distinction an agent could otherwise get wrong given the sibling 'get-event'/'list-events' family.

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?

Usage is implied by the consequence stated ('new events of this type are rejected'), so an agent can infer this is for stopping future event ingestion. But it never names an alternative or exclusion — e.g. when to use update-workspace-event to disable instead, or whether this affects existing automations that reference the event.

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