Delete a post / page

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

With no annotations, the description carries full responsibility and explains that default is recoverable trash, while force:true is permanent and irreversible. It adds the crucial safety note about confirming with the user, which is essential for a destructive tool.

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 two sentences, front-loaded with the primary action, and every clause provides meaningful information. No filler or redundancy.

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?

The tool is a straightforward destructive operation, and the description covers the key behavioral distinction (trash vs permanent) and user confirmation. Parameter guidance is left largely to schema, and the absence of output schema is acceptable because the main concern is the side effect.

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 already covers 75% of parameters with descriptions. The description adds 'recoverable' and the confirmation nuance for force, but largely repeats the schema's 'irreversible delete'. It does not add meaning for the required id parameter, so the extra contribution is limited.

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 ('Move an item to trash', 'delete permanently') and the resource (a post/page). It distinguishes the tool from siblings like wp_create_content, wp_update_content, and wp_get_content by focusing on deletion semantics.

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?

It provides explicit guidance on when to use force:true versus the default trash behavior, including the caution to confirm with the user. It does not name alternative tools for non-destructive actions, but the intended use case is clear.

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