Remove a menu item

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

The description adds substantial behavior beyond the annotations: sub-items keep the removed item as parent and may surface at top level, the call returns deleted and item_id, invalid ids are refused, and permissions can be withheld per item. It also emphasizes permanence and lack of undo, which is critical for a destructive operation.

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 core action is front-loaded, and each subsequent sentence adds distinct operational value: side effects on sub-items, return values, idempotent-ish refusal behavior, permissions, and permanence. There is no filler.

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 output schema, the description is complete: it covers return values, permissions, permanence, side effects on child items, and behavior for invalid ids. An agent has enough information to call it correctly and understand the consequences.

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 item_id meaning is already documented in the schema. The description reinforces that it targets one menu item, but does not add format or lookup details beyond what the schema already provides, so the baseline of 3 applies.

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 specific verb and resource: remove one item from a navigation menu by item_id. It also immediately clarifies that the linked post/page is untouched, which distinguishes this from wp_delete_post and makes the scope unambiguous.

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?

It gives clear when-to-use and when-not-to-use context: use it only for menu items, not for the linked content, and note that this is permanent rather than a trashable delete. It also explains what happens to sub-items and to repeated calls on non-menu-item ids.

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