wordpress_create_menu

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

With no annotations provided, the description carries full burden but discloses minimal behavioral traits. It mentions the side effect of assigning to theme locations, but fails to state this is a persistent write operation, lacks idempotency notes, error handling details, or return value description.

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?

Two sentences with minimal waste, but the '[UNIFIED]' prefix appears to be metadata cruft rather than descriptive content. Given the lack of schema documentation, the description is actually undersized rather than optimally concise.

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?

Inadequate for a resource-creation tool with zero schema descriptions and no output schema. Missing explanation of return values (created menu ID/data), no detail on required vs optional parameters beyond the locations hint, and no WordPress-specific context (e.g., theme location registration requirements).

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 has 0% description coverage. The description only implicitly references the 'locations' parameter ('assign to theme locations') and provides no semantic information for 'site', 'name', or 'slug' (e.g., that slug is optional or auto-generated when null).

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?

States specific verb ('Create') and resource ('navigation menu'), and mentions the optional theme locations feature. However, it does not explicitly distinguish from sibling tool 'wordpress_create_menu_item' (container vs. item), which could cause confusion given both exist on this server.

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 no guidance on when to use this versus 'wordpress_update_menu_item' or other menu management tools. No prerequisites mentioned (e.g., site must exist). No mention of error conditions like duplicate menu names.

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