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

Beyond the destructiveHint annotation, the description discloses irreversibility ("permanently"), the blast radius (live platform posts are not removed), the required auth scope, and the recommended human confirmation step. These are exactly the extra facts an agent needs before firing 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?

Front-loaded and compact, with the destructive nature stated first. The leading "[DESTRUCTIVE] DESTRUCTIVE:" duplication wastes a few tokens, but every other clause carries unique information.

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 single-parameter destructive delete with no output schema, the description covers everything material: scope, irreversibility, what is and is not affected, auth requirement, and confirmation policy. Nothing needed to invoke 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?

The schema has 0% description coverage and the single `id` parameter is undocumented, but the description compensates partially by anchoring it via "content item from the library" and the DELETE /api/v2/content/{id} path, implying the id is a content item identifier. It does not state the id format (numeric vs. string/UUID), so the gap is only partly closed.

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 ("permanently deletes a content item from the library") and clarifies the boundary against related operations by noting that already-published posts are untouched. The resource noun cleanly separates it from delete_experiment, delete_queue and delete_text_template.

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 precondition ("Needs the `write` scope") and an explicit behavioral instruction ("Ask the user before calling"), which is strong when-to-use guidance for a destructive tool. It stops short of naming an alternative sibling, so it is clear context rather than full when/when-not routing.

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