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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false, so the safety profile is largely covered. The description still adds real value beyond them: irreversibility ('cannot be undone'), the preservation guarantee for approved posts, and a required confirmation step. It does not say what happens if both parameters are supplied or omitted, or what the call returns.

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 destructive scope first, the safety caveat second. No filler, and the irreversible warning is placed where an agent will read it before acting.

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 destructive, no-output-schema tool, the description covers scope, preservation of approved posts, irreversibility, and the confirmation duty – enough to act safely. Remaining gaps are argument-selection rules (both/neither) and any return value such as the affected post count.

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 0%, so the description must carry the meaning – and it does, explaining that `plan_id` targets a plan's waiting posts and `social_group_id` targets a group's waiting posts, with 'or' signalling alternatives. It never states that both are optional and mutually exclusive, nor the behavior when neither or both are passed.

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?

Names a specific verb (removes) and a precisely scoped resource: only posts 'still waiting for review' under a plan, or waiting posts of a social group. The scoping clause 'Approved posts are never touched' implicitly separates it from single-post sibling remove_plan_post, but no sibling is named explicitly.

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 when-to-use conditions for both modes (`plan_id` vs `social_group_id`) and an explicit operational rule: ask the user before discarding and state how many posts will be removed. It does not point to `remove_plan_post`/`list_plan_posts` as alternatives when the intent is a single post or a review first.

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