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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description adds value beyond them: the cascade effect ('an event is cancelled for those who signed up, and they're told'), irreversibility, and the enforced confirmation workflow. This is exactly the side-effect disclosure an agent needs before a destructive call.

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 cascade/irreversibility risk and the required confirmation are both front-loaded in parentheses and after the colon respectively, with zero filler.

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?

With an output schema, full parameter coverage, and annotations covering the safety profile, the description supplies the remaining needed context: authorization scope, cascade behavior, and the mandatory confirmation protocol. Nothing required to call it correctly 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 both parameters are already documented, which sets the baseline at 3. The description adds meaning to confirm by tying it to the human-confirmation step ('ask the person, then call with confirm: true'), clarifying it is a consent gate rather than a mere flag.

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 ('Delete a post') plus the scope constraint (a channel the person runs or edits), so an agent can distinguish it from edit_post or create_post without inspecting schemas.

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?

The description gives a concrete procedural rule for invocation ('ask the person, then call with confirm: true') and constrains usage to posts the person owns or edits. It never names a sibling alternative (e.g., edit_post) for the case where deletion is not intended, so it stops short of full when/when-not guidance.

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