Delete WordPress Page

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

The description adds meaningful behavior beyond the annotations: it explains the default behavior (trash) and the force option (permanent deletion). It also points to the return shape via 'see wp_delete_post for shape'. This enriches the safety profile already indicated by destructiveHint=true and readOnlyHint=false, giving the agent operational detail.

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 tightly structured with a one-sentence summary, a labeled Args list, and a Returns line. It is concise, avoids redundancy, and every sentence adds value.

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 deletion tool with a moderate complexity (3 parameters, 1 required), the description covers the critical aspects: what it deletes, how to control trash vs permanent, and where to find the return shape. It does not provide a detailed return format, but the reference to wp_delete_post and the presence of an output schema for that sibling reduces the need. Minor gaps include error handling and idempotency, but these are not essential.

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 input schema covers 100% of parameters with descriptions that match the description text exactly. The description adds no new meaning beyond the schema—it essentially repeats the schema's parameter descriptions, so the baseline score of 3 is appropriate.

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 page') and the target resource ('a page'). It differentiates from sibling tools like wp_delete_post by naming 'page' specifically, though it does not explicitly contrast itself against alternative deletion tools.

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: use this tool when you need to delete a page. It does not provide explicit guidance on when to choose this over alternatives like wp_delete_post, nor does it mention any preconditions or exclusions. The mention of 'see wp_delete_post for shape' hints at a relationship but doesn't clarify selection criteria.

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