wordpress_delete_page

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

With no annotations, the description must fully explain behavior. It mentions deletion/trashing but does not clarify the effect of the 'force' parameter, whether deletion is reversible, or what permissions are needed. This is insufficient for safe invocation.

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 very concise at two sentences and places the key requirement upfront. However, it could be slightly more explicit about the 'force' parameter without losing brevity.

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?

Given the lack of output schema, annotations, and parameter descriptions, the description is severely incomplete. It omits details about error handling, return values, and the difference between trash and permanent delete, leaving critical gaps for a delete operation.

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 only mentions 'confirmDelete' without explaining its meaning or the roles of 'id' and 'force'. The parameters remain largely unexplained, adding almost no value beyond the schema.

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 or trash') and the resource ('a WordPress page'), making the tool's purpose immediately obvious. It differentiates from siblings like wordpress_delete_post by specifying 'page'.

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 only usage condition mentioned is 'Requires confirmDelete=true', which is helpful. However, no guidance is given on when to use this tool versus alternatives like wordpress_delete_post or wordpress_update_page_status, leaving the AI without context for selection.

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