wordpress_delete_post

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

With no annotations, the description carries full behavioral burden. It explicitly discloses the critical behavior of the force parameter (permanent vs trash), which is valuable. However, it omits other potential traits like permission requirements, error handling, or irreversibility confirmation beyond 'permanently delete'.

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?

A single, concise sentence that is front-loaded with the core action ('Delete a post') and efficiently packs the conditional behavior. No wasted words, ideal for quick agent parsing.

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 two-parameter tool with no output schema, the description covers the essential operational behavior. It lacks some completeness (e.g., return values, error cases), but the minimal complexity makes this acceptable. The trash/permanent distinction is the most important contextual complexity and is addressed.

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 0%, so the description must compensate. It effectively explains the force parameter's meaning (permanent vs trash), which adds essential semantics beyond the bare schema type. The postId parameter is self-explanatory, but the description does not explicitly label it as the target post ID.

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 uses a specific verb+resource ('Delete a post') and clearly distinguishes the two deletion modes (force=true permanent vs trash). This is unambiguous and implicitly differentiates from sibling tools like bulk_delete_posts and delete_page via the 'post' scope.

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 implies usage by context (single post deletion vs bulk or page deletion) but does not explicitly mention alternatives or when-not-to-use. There is no exclusionary guidance like 'use wordpress_bulk_delete_posts for multiple posts,' so guidance is only implied.

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