wordpress_delete_menu

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

There are no annotations, so the description must carry the burden of behavioral disclosure. While 'Delete' implies destruction, it does not explain whether deleting a menu cascades to menu items, whether the operation is reversible, or what permissions are required. The 'force' parameter's behavioral role is also unexplained.

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, efficient sentence with no wasted words. It is well-structured for readability but is overly terse given the tool's destructive nature and reliance on parameter clarification.

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 two required parameters, no annotations, and no output schema, this description is critically incomplete. It omits the meaning of 'force', the effects on related menu items, and any usage caveats, leaving the agent without essential context to invoke the tool safely.

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%, and the description adds no meaning to the parameters. 'menuId' and 'force' remain unexplained, especially 'force', which is ambiguous. The description must compensate for the schema gap but fails to do so.

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' uses a specific verb (delete) and resource (navigation menu), clearly distinguishing it from sibling tools like wordpress_delete_menu_item and wordpress_delete_page. It directly states the tool's core function 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?

No guidance is provided about when to use this tool versus alternatives such as deleting menu items, deleting pages, or other delete operations. The description gives no context about prerequisites or conditions for use.

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