wp_remove_menu_item

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

With no annotations provided, the description carries the full burden. It explicitly discloses the non-destructive default (dry_run=true returns a preview), the side effect of removing only the menu item (not the page), and the production safety gate (allow_prod=true).

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 concise and well-structured, using line breaks to emphasize key points. Every sentence adds value without redundancy, making it easy to parse quickly.

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?

The description adequately covers the tool's behavior and safety considerations, but it omits details about the return value or output format (e.g., what the preview or success message looks like). This is a minor gap given the tool's simplicity.

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 no parameter descriptions, but the tool description explains three of four parameters clearly: item_id (with a crucial disambiguation), dry_run (with its effect), and allow_prod (with its permission role). The 'install' parameter is not explained, leaving a small gap.

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 tool's purpose: 'Remove one item from a navigation menu' with a specific verb and resource. It also clarifies a key distinction ('the page it links to is NOT deleted'), which differentiates it from other page-related operations.

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?

Provides practical usage instructions such as the defaults for dry_run and allow_prod, and the requirement for REST transport. While it does not explicitly contrast with sibling tools like wp_update_menu_item, the name and description make the appropriate usage evident.

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