wp_create_menu

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

With no annotations, the description must disclose behavioral traits. It only mentions dry-run support, which is helpful, but omits details like whether creation overwrites existing menus, enforces uniqueness, or requires authentication. The mutation side effect is implied but not explicit.

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 short sentences with no fluff. It is front-loaded with the core action. However, it could add a bit more context without losing conciseness (e.g., mentioning required name).

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?

With 6 parameters, no annotations, and no output schema, the description is severely incomplete. It does not explain the meaning of 'classic menu', required parameters, or side effects. An agent would have to infer too much to call this 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?

Schema description coverage is only 17% (only dry_run has a description). The description adds nothing about name, slug, auto_add, locations, or description. It only reinforces dry-run, which is already in the schema. Fails to compensate for low coverage.

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 states a specific verb ('Create') and resource ('classic menu'), which is clear and distinguishes it from list/update/delete menu siblings. However, 'classic' is not explicitly contrasted with modern/block-based menus, leaving slight ambiguity about scope.

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. It does not mention prerequisites (e.g., existing menu locations) or when to prefer wp_update_menu or wp_create_menu_item. The dry-run mention hints at preview usage but does not clarify selection criteria.

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