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

The description adds substantial behavior beyond the annotations: the edit_theme_options capability requirement, the undo behavior ('deletes the item while it is unchanged'), and the Royally approval gate where nothing changes until a person approves. These details are not present in the structured annotations and materially affect how an agent should plan the call.

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 front-loaded with the core action and then carries prerequisites, capability, undo, site, and approval details. It is appropriately sized, though the parenthetical site note and Royally sentence make it slightly dense.

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 mutation tool with no output schema, the description covers the key safety and workflow context: capability requirement, menu prerequisite, undo behavior, and approval gating. It does not describe the return value, such as the created menu item ID, which would help follow-up calls.

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 78%, so most parameters are already documented in the schema. The description adds useful context that menu_id can be obtained via wp_create_menu, but it does not clarify the required title or menu_id parameters or the url/object_id linkage beyond what the schema already says.

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: 'Create a menu item in a navigation menu.' It also distinguishes the tool from wp_create_menu by explaining when to call wp_create_menu first to obtain a menu_id.

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 preconditions and one explicit alternative: on a site with no menus, call wp_create_menu first, and the caller must have edit_theme_options capability. It does not explicitly contrast with wp_update_menu_item or wp_delete_menu_item, but the create semantics are clear.

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