wordpress_create_menu

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

No annotations are provided, so the description carries full burden. 'Create a new navigation menu' implies a write/mutation operation, but it doesn't disclose behavioral traits like required permissions, whether menus can be created with specific settings or locations, what happens if a menu with the same name exists, or what the tool returns. This leaves significant gaps for an agent to understand how to use it effectively.

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 a single, efficient sentence that gets straight to the point with no wasted words. It's appropriately sized for a simple creation tool and front-loads the essential action.

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 annotations, no output schema, and minimal parameter documentation, the description is insufficient. It doesn't address what the tool returns, error conditions, or how it interacts with sibling menu tools. Given the complexity of WordPress menu management and the lack of structured data, more context is needed for an agent to use this tool correctly.

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 1 parameter with 0% description coverage, and the tool description doesn't mention any parameters. The description doesn't add meaning beyond the schema, but since there's only one parameter and the purpose is clear, the baseline is appropriate. However, it doesn't explain what the 'name' parameter represents or any constraints on it.

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 'Create a new navigation menu' clearly states the verb ('create') and resource ('navigation menu'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'wordpress_create_menu_item' or 'wordpress_assign_menu_to_location', which would require more specificity about what exactly is being created.

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 provides no guidance on when to use this tool versus alternatives. With siblings like 'wordpress_create_menu_item' (for adding items to menus) and 'wordpress_assign_menu_to_location' (for placing menus), there's no indication of prerequisites, sequencing, or distinctions between these related menu operations.

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