wp_delete_page

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

No annotations are provided, so the description carries the full behavioral burden. It says 'delete' but never discloses whether the page is trashed or permanently removed, whether it is recoverable, what happens to child pages or associated media, or what occurs if the ID does not exist — all critical for an irreversible-looking mutation.

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?

A single tight sentence with the action and resource front-loaded and no filler. It is efficient, though it is minimal to the point of under-specification rather than optimized conciseness.

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 destructive single-target operation with no annotations and no output schema, the description omits the facts an agent most needs: permanence/trash semantics, permission requirements, and error behavior. The safety and side-effect picture is left entirely to inference.

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 100% and only one parameter exists, so the schema already documents the integer id as 'Page ID'. The description's 'by ID' adds no format, validity, or lookup guidance beyond that, making 3 the correct baseline.

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?

States a specific verb and resource ('Delete a WordPress page') with the identifier scope ('by ID'), which separates it from wp_delete_post and the other delete_* siblings in the family. It does not explicitly name the alternative, but the noun choice is precise enough that an agent can pick the page variant without opening the schema.

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?

No indication of when this tool is appropriate versus wp_update_page, wp_get_page, or its closest sibling wp_delete_post. There is also no mention of prerequisites such as required capabilities or whether the operation needs confirmation, so selection guidance is effectively absent.

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