wordpress_delete_page

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Delete a page' implies a destructive operation, but it doesn't mention permissions required, whether deletion is permanent or reversible, what happens to associated content, or any rate limits. For a destructive tool with zero annotation coverage, this is dangerously inadequate.

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 maximally concise - just three words. While it's severely under-specified, it's not verbose or poorly structured. Every word earns its place, though more content would be needed for completeness.

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 2 parameters (0% schema coverage), no annotations, no output schema, and many similar sibling tools, this description is completely inadequate. It doesn't explain what constitutes a 'page' in WordPress, doesn't cover parameters, doesn't mention behavioral implications, and provides no usage context.

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?

The schema has 2 parameters with 0% description coverage, and the tool description provides zero information about what 'pageId' or 'force' mean. The description doesn't mention parameters at all, leaving the agent with no semantic understanding of what values to provide or what 'force' does in the context of page deletion.

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 'Delete a page' clearly states the action (delete) and resource (page), which is better than a tautology. However, it doesn't distinguish this tool from similar sibling tools like 'wordpress_delete_post' or 'wordpress_delete_media' - it's unclear what makes a 'page' different from other deletable content types in WordPress.

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 provides absolutely no guidance on when to use this tool versus alternatives. With sibling tools like 'wordpress_delete_post', 'wordpress_delete_media', and 'wordpress_bulk_delete_posts', there's no indication of when a page deletion is appropriate versus post deletion, nor any prerequisites or constraints mentioned.

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