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

The description explicitly says the deletion "cannot be undone with a tool" and requires user confirmation before each call, which is a destructive, irreversible act — yet the annotations declare destructiveHint=false. This directly contradicts the structured safety signal an agent relies on, so the description scores 1 despite being otherwise informative about confirmation and credentials.

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 purpose is front-loaded in the first two sentences and each subsequent sentence carries a distinct fact (irreversibility, confirmation policy, audience reach, credential requirement). The browser-specific aside "as the red X on the Events page does" is the only sentence that doesn't fully earn its place.

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 one-parameter delete with no output schema, the description covers the essentials an agent needs: irreversibility, the need for user confirmation, and the required credential scope. Its completeness is undermined only by the inconsistency with the destructiveHint annotation, which is scored separately.

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?

There is a single parameter and schema description coverage is 100% ("Event ID from list_events."), so the schema fully carries the parameter semantics. The description adds nothing about the event_id, which matches the baseline of 3 when the schema does the heavy lifting.

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 ("Remove an event from your artist page", "Deletes one event") and bounds the scope to a single event on the artist's own page. It is unambiguous against siblings like bandsintown_update_event or bandsintown_create_event, though it never explicitly names an alternative, so it stops short of a 5.

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 gives clear operating context: per-call confirmation is on by default and can be turned off, the user must be consulted before each call because it "reaches other people," and an API key with access to the app is required. What is missing is guidance on when to choose delete versus the sibling update/publish tools; the mention of re-creating the event is about undoing, not tool selection.

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