Delete WordPress Post

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

Beyond the annotations (destructiveHint=true), the description discloses the default trash behavior, 30-day recoverability, and the effect of force=true. It also outlines the exact return payload for both modes, offering rich behavioral context. This exceeds what the annotations provide and fully clarifies the tool's side effects.

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 well-structured with clear 'Args' and 'Returns' sections. Every sentence serves a purpose: the first explains the core behavior, the Args bullet list specifies inputs, and the Returns section clarifies outcomes. No fluff or redundancy; it is concise yet highly informative.

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?

With three parameters, all explained, and no output schema, the description fully compensates by detailing return values for both force modes. It covers edge cases (trash vs. permanent deletion) and output format options. The description is complete for an agent to invoke the tool correctly without additional context.

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%, so parameters are already documented. The description adds value by explicitly linking each argument to its behavioral impact, especially in the 'Returns' section showing how force=false returns a trashed post object and force=true returns a deleted flag and previous object. This goes beyond the schema's static definitions.

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 opens with 'Delete a post', using a specific verb and resource. It further distinguishes by explaining the trash vs. permanent deletion behavior, which clearly separates it from sibling tools like wp_delete_page or wp_delete_media. The title and description align perfectly with the tool's functionality.

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 implies when to use the tool (deleting posts) and explains the force option for permanent deletion. However, it does not explicitly contrast with alternative tools (e.g., wp_delete_page) or state when not to use it. The context is clear but lacks explicit exclusion guidance.

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