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

Annotations already declare destructiveHint=true, so the safety profile is known; the description adds real value on top by disclosing platform coverage limits and the partial-operation outcome (Instagram/TikTok silently skipped). It does not say whether deletion is irreversible, whether failures on one platform abort the rest, or how results are reported.

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?

Three short sentences, front-loaded with the action and scope, then the platform whitelist, then the exception. Every sentence carries distinct information with no 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?

For a destructive bulk tool with no output schema, the description covers what gets deleted and what is deliberately left behind, which is the key risk an agent needs. It leaves a gap around what a partial failure returns and whether already-unpublished posts cause errors.

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% for the single launch_id parameter, so the schema already carries the semantics. The description only implies the launch scoping ('for a launch') without adding format or identifier guidance beyond the schema.

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 (delete), resource (published posts) and scope (all posts for a launch), which implicitly separates it from the singular delete_post sibling. It does not explicitly name an alternative, but the bulk-for-a-launch framing is unambiguous.

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 clear condition for use (tear down all published posts for a launch) and, more usefully, an explicit exclusion: Instagram and TikTok are skipped and require manual deletion. It stops short of pointing to a per-post fallback tool for those platforms.

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