Delete Navigation Menu

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

Beyond annotations (destructiveHint=true), the description adds that the deletion is permanent, includes 'all its items', and is a 'force delete'. It also states the admin requirement, giving valuable behavioral context without contradicting 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 brief and front-loaded with the most critical information (permanent deletion, admin requirement). The Args list is clearly formatted and every sentence contributes to understanding the tool's purpose and constraints.

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?

With 100% schema coverage and strong annotations, the description is sufficiently complete for a simple delete tool. It covers irreversibility, admin requirement, and the fact that all menu items are affected. Minor omissions (e.g., exact return behavior) are acceptable given the response_format parameter and lack of output schema.

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 coverage is 100%, so the baseline is 3. The description's Args section repeats the schema's parameter details (menu_id, response_format) without adding additional semantic meaning beyond what the schema already provides.

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 specific action: "Permanently delete a navigation menu and all its items (force delete)." It names the resource (navigation menu) and the scope (all items), distinguishing it from sibling tools like wp_delete_menu_item.

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 clear context for usage: requires admin and is irreversible via the API. It doesn't explicitly name alternatives, but these operational caveats effectively guide when to use it, meeting the bar for clear context without exclusions.

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