wp_delete_content

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

No annotations are provided, so the description carries the full behavioral burden. It explicitly discloses the default trash behavior and the force=true permanent delete option, which is the central safety-relevant distinction for deletion. It does not mention permissions or side effects on related data, but the key destructive behavior is transparent.

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?

The description is a single, front-loaded sentence with no filler. It communicates the action, resource, default behavior, and the force option efficiently without any wasted words.

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 simple 3-parameter delete tool with no output schema and no annotations, the description covers the operation, target content types, default behavior, and the force option. It doesn't describe return values, but with 100% schema coverage and a clear purpose, nothing critical is missing for invoking the tool correctly.

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%, so the schema already documents all three parameters. The description adds context that type accepts post/page/product and that force defaults to false, but this mostly restates the schema's own descriptions. Baseline 3 applies since 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?

The description states a specific verb ('Delete') and resource ('WordPress post, page, or product'), clearly distinguishing it from sibling delete tools like wp_delete_plugin, wp_delete_comment, wp_delete_media, and wp_delete_option. It leaves no ambiguity about what content type this tool operates on.

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?

The description clearly scopes the tool to posts, pages, or products, which implies when to use it versus other delete tools. It does not explicitly name alternatives or exclusion conditions, but the scope is specific enough that an agent can confidently select it for content deletion.

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