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

Annotations already flag destructive=true and idempotent=true, so the description's job is to say what actually gets destroyed, and it does: drafts/pending posts, an entire group when the post belongs to one, plus automatic cancellation of pending delivery. It also discloses the blocking precondition (a published or processing member) and an explicit non-effect (published network content survives), which is precisely the context annotations cannot carry.

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?

Four short sentences, front-loaded with the core action and then the cascade, the blocking condition, and the exclusion. No sentence is redundant, and each one carries a distinct behavioral fact.

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 destructive tool with full annotation coverage and no output schema, this covers the essentials: what qualifies for deletion, what cascades, what blocks it, and what is preserved. Nothing an agent needs in order to decide to call it 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?

There is a single parameter, postId, and schema description coverage is 100%, so the schema already documents it fully. The description adds no extra meaning about accepted ID formats or whether group member IDs are valid inputs; baseline 3 applies 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?

States a specific verb and resource (delete a draft or pending post) and narrows the scope twice: it explains that pending deliveries are cancelled and that already-published content is not touched. That scoping lets an agent distinguish it from publish_post, update_recurring_post, or delete_media without opening any schema.

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 clear applicability conditions: only unpublished drafts or pending posts, group posts cascade, and published/processing group members block the call. It stops short of naming a sibling to use instead when the target is already published, so the when-not path is stated but the alternative route is left implicit.

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