wordpress_delete_page

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

With no annotations, the description carries the burden and discloses the key destructive behavior: force=true permanently deletes while force=false moves to trash. It also states a confirmation is returned, but it does not mention permission requirements or failure behavior.

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 compact and front-loaded with the purpose, followed by clearly labeled Args and Returns sections. Every line adds useful information, with no redundancy or filler.

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 simple deletion tool with two parameters and an output schema, the description adequately covers the operation, including the trash/permanent distinction and return confirmation. It could add edge-case behavior, but nothing critical is missing for selecting and invoking this tool correctly.

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?

Although the input schema lacks descriptions, the Args section explains both parameters in plain terms: page_id identifies the page and force controls trash vs permanent deletion. This fully compensates for the 0% schema coverage.

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 opening sentence 'Delete or trash a WordPress page' states a specific action and resource, and the title/description make it clear this targets pages rather than posts/media. This distinguishes it from siblings like wordpress_delete_post and wordpress_delete_media.

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 communicates that this is for deleting or trashing WordPress pages, which establishes the use context by resource. It does not explicitly name alternatives or state when not to use it, but the page-specific scope is sufficiently clear.

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