wp_delete_post

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

No annotations are provided, so the description carries full burden. It discloses the trash vs permanent behavior but omits side effects (e.g., metadata deletion), required permissions (e.g., delete_posts capability), and whether the operation is reversible. For a destructive tool, this is insufficient.

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 sentence with no wasted words. It efficiently conveys the core action and the key variant behavior.

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 two parameters and no output schema, the description covers the main behavior but lacks details on return values, error conditions, and safety context. It is adequate but not fully complete for a mutation tool.

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 description adds value beyond the schema by summarizing the effect of the force parameter: 'moves to trash, or permanently if force=true'. This clarifies the interaction between the two parameters. Schema coverage is 100%, so baseline is 3, but the concise summary merits a higher score.

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 clearly states the action ('delete a post') and specifies the two modes (trash vs permanent with force=true). It distinguishes the tool from sibling tools like wp_delete_page or mcp_delete_cpt_post by explicitly mentioning 'post' and the dual behavior.

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 does not explicitly guide when to use this tool versus alternatives (e.g., wp_delete_page for pages). However, the name and content make it clear it's for WordPress posts, providing implicit guidance.

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