wordpress_create_menu

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

No annotations exist, so the description must inform behavioral traits. It only states creation and optional location assignment, omitting permissions, side effects, rate limits, or any other behavioral details.

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?

Description is very short (one sentence) and front-loaded with key information. However, it may be too concise, sacrificing necessary detail for brevity.

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?

No output schema, no annotations, and 4 poorly documented parameters. The description fails to provide a complete picture of the tool's behavior, return values, or parameter constraints.

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 coverage is 0%, and description adds minimal parameter context: only mentions 'assign to theme locations' (related to locations parameter). No explanation for name, site, or slug.

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 the tool creates a new navigation menu and optionally assigns to theme locations, which is specific and distinguishable from sibling tools like wordpress_list_menus or wordpress_create_menu_item.

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?

No guidance on when to use this tool versus alternatives (e.g., wordpress_create_menu_item) or when not to use it. No prerequisites or context provided.

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