wp_delete_page

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

With no annotations, the description must carry the full behavioral disclosure burden. It only states the destructive action and the credential prerequisite; it does not say whether deletion is permanent or moves to trash, what the force parameter changes, or what side effects may occur. The verb 'Delete' merely restates the tool name, leaving only the auth note as incremental 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 exactly two sentences and both are necessary: the first states the action, the second states the setup requirement. It is front-loaded with the core purpose and contains no filler, making it a model of concise structure.

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 tool with no annotations and no output schema, this description is too sparse. It omits parameter semantics, force behavior, permanence, and side effects. While the tool is simple on the surface, the missing nuance around deletion behavior makes the context incomplete for safe invocation.

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 for the undocumented parameters. It does not explain what id refers to or what force does, even though force is a boolean whose behavior is ambiguous. An agent must guess whether force controls permanent deletion, bypassing trash, or ignoring errors.

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 states a precise verb and resource: 'Delete a WordPress page.' This clearly distinguishes it from sibling tools like wp_delete_post (which targets posts) and wp_update_page (which updates rather than deletes). The credential requirement is additional context, not a distraction.

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 gives no guidance on when to prefer this tool over alternatives, when not to use it, or how it relates to wp_delete_post or force behavior. The required-credentials note is a prerequisite, not a usage criterion, so an agent gets little routing help.

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