Build a Whole Menu in One Command

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

Beyond the annotations, the description discloses that it creates a NEW menu and explicitly does not merge, which is critical for understanding side effects. It also explains item linking semantics and return values, providing full behavioral context.

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 well-structured with introduction, args, example, and return note. Every sentence adds value—no filler or repetition of schema details. Despite length, it remains efficient and information-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?

Given the tool's complexity and lack of output schema, the description fully covers return format, behavior around creating vs merging, replacement guidance, and parameter relationships. Nothing important is left unexplained.

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 description adds substantial meaning beyond the schema: it explains how items map to submenus, ordering follows array order, and the example clarifies page_id vs url vs neither. This enriches the schema's already high coverage with practical usage semantics.

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?

Description clearly states a specific action: creating an entire navigation menu with nested submenus, ordering, and theme-location assignment. It distinguishes itself from sibling tools like wp_create_menu or wp_create_menu_item by emphasizing whole-menu construction from a single spec.

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?

Explicitly says it is ideal for rebuilding primary navigation by command and even advises using wp_list_menus / wp_delete_menu first when replacing. This gives clear when-to-use and alternative guidance.

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