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

Goes well past the destructiveHint/idempotentHint annotations by enumerating what is destroyed (participation, invitation, tickets), what is preserved (the account), and the non-obvious silent-success behavior when the email matches nobody. The confirm-gated preview path is a behavioral trait an agent could not infer from annotations alone.

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?

Front-loads the two highest-risk facts ('WRITE, IRREVERSIBLE') in the first three words, then packs scope, edge-case behavior, and the confirm requirement into a single dense paragraph with no filler. The endpoint suffix is the only mildly 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?

There is no output schema, yet the description still covers the two response shapes that matter: successful deletion and the silent-success-on-no-match case, plus the preview returned without confirm. Nothing an agent needs in order to call this destructively and safely is missing.

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%, so the baseline is 3, but the description adds interpretive value: the silent-success note tells the agent that an unknown email is not an error, which changes how the email argument should be validated and reported. The confirm gate is restated from the schema rather than extended, keeping this below a 5.

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 ('remove the person with this email from the event') and immediately delimits the blast radius: participation, invitation and tickets for this event are deleted while the Eventee account survives. That scope statement is what separates it from registrations-level siblings such as eventee_remove_registration.

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?

Gives a concrete operating precondition — 'Needs confirm: true (without it: a preview, nothing removed)' and 'ask the user to approve first' — which tells the agent exactly how to sequence the call. It never names an alternative sibling or an explicit when-not-to-use case, so it falls short of a 5.

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