Create Navigation Menu

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

Beyond annotations, the description adds an authorization requirement ('Requires admin') and return value ('Returns the new menu ID'). However, it does not disclose potential side effects of theme location assignment, such as overriding existing location assignments, which could be relevant given openWorldHint=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 opening sentence is concise and front-loaded with the core behavior. The Args list is somewhat redundant with the schema, adding minor waste, but overall the description remains brief and readable.

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 simple creation tool, the description covers the purpose, parameters, return value, and auth requirement. The lack of output schema is compensated by the explicit return ID. However, the undisclosed side effects of location assignment leave a minor gap in completeness.

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 input schema already provides descriptions and examples for all three parameters, so the Args section in the description adds no new meaning. It merely repeats the schema information, thus offering marginal value.

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 it creates an empty navigation menu and optionally assigns theme locations, distinguishing it from related tools like wp_update_menu and wp_create_menu_item. The verb 'Create' and resource 'navigation menu' are specific, and the scope ('empty') adds clarity.

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 implies use for initial menu creation, but it does not explicitly mention alternative tools or exclusions. Sibling tools like wp_create_menu_item or wp_update_menu are not referenced, so the guidance relies on implicit context.

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