wp_delete_page

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

Annotations already cover the destructive nature (destructiveHint=true) and readOnlyHint=false. The description adds no additional behavioral context such as permanence of deletion, cascading effects, permission requirements, or whether the page is moved to trash. This provides no extra transparency beyond the annotations.

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 a single, concise sentence that directly states the tool's purpose without unnecessary words. It is appropriately sized for a tool of this simplicity, though it omits some potentially useful context.

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 tool's low complexity, annotations, and full schema coverage, the description is just sufficient. However, it does not mention return values or side effects, and with no output schema the agent relies on assumed delete semantics. This is acceptable but not complete.

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% with the single parameter 'id' documented as 'Page ID to delete.' The tool description adds no further semantic detail, so the baseline of 3 is appropriate given the schema already fully documents the parameter.

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) and the specific resource (WordPress page), unambiguously distinguishing it from sibling tools like wp_delete_post which targets posts. It directly answers what the tool does without ambiguity.

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?

There is no guidance on when to use this tool versus alternatives, nor any mention of prerequisites, exclusions, or context such as 'use this for page-type content only.' The description only states the action without any usage context.

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