wordpress_delete_menu

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'Delete' implies a destructive operation, the description doesn't specify whether deletion is permanent, requires admin permissions, affects associated menu items or locations, or what happens on success/failure. For a destructive tool with zero annotation coverage, this represents significant behavioral gaps.

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 with a single clear sentence: 'Delete a navigation menu.' There's no wasted language or unnecessary elaboration, making it easy to parse and understand at a glance.

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 required parameters, 0% schema coverage, no annotations, and no output schema, the description is severely incomplete. It doesn't explain what the tool returns, what the parameters do, what permissions are required, or how the deletion affects the WordPress ecosystem. The description fails to provide the necessary context for safe and effective tool 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?

With 0% schema description coverage for both parameters (menuId and force), the description provides no information about what these parameters mean or how they affect the deletion. The description doesn't mention parameters at all, failing to compensate for the complete lack of schema documentation. This leaves the agent with no semantic understanding of required inputs.

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 navigation menu' clearly states the verb ('Delete') and resource ('navigation menu'), making the purpose unambiguous. However, it doesn't distinguish this tool from sibling deletion tools like wordpress_delete_menu_item, wordpress_delete_page, or wordpress_delete_post, which all perform similar destructive operations on different WordPress resources.

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 no guidance on when to use this tool versus alternatives. There's no mention of prerequisites (e.g., needing menuId), when deletion is appropriate, or what happens to associated menu items. With many sibling deletion tools available, this lack of differentiation leaves the agent guessing about appropriate use cases.

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