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

Goes well beyond destructiveHint=true by disclosing the exact cascade: media and thumbnails removed, all scheduled/queued/draft posts from the upload cancelled, already-published posts left live. It also states irreversibility and a permission restriction (workspace clients), which the annotations cannot express.

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?

Five short sentences, front-loaded with what is deleted, then consequences, then the safety instruction. Every sentence carries distinct information — cascade, published-post exception, irreversibility, permission — 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 mutation with no output schema, this covers the full decision surface: scope, side effects, exception for published content, irreversibility, and authorization limits. Nothing an agent needs before invoking 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?

Schema description coverage is 100% and both parameters are documented in-schema, including the idempotency key's retry window. The description adds no additional parameter meaning, so the baseline of 3 applies.

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 (deletes) and resource (an upload) and enumerates the covered media types (video, image, carousel, text post), so the agent knows exactly what object class is affected. The analogy to the ShortSync dashboard anchors the semantics without ambiguity.

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 operating conditions: confirm with the user first, and workspace clients can't delete — that rules out a whole caller class. It does not, however, route to the sibling alternative delete_published_post, which is the obvious choice when the target is an already-published post rather than a library upload.

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