wp_create_menu_item

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

No annotations are present, so the description carries a heavy burden for behavioral disclosure. It adds 'Supports dry-run,' but the schema already states this for the dry_run parameter. It does not disclose side effects, required permissions, validation behavior, or whether any output or confirmation is returned.

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 front-loaded and free of filler: 'Create classic menu item. Supports dry-run.' Each sentence earns its place. It is concise, but it leans closer to under-specification than optimal compression given the tool's complexity.

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?

A 15-parameter creation tool with no annotations, no output schema, and a two-sentence description is far from complete. The agent cannot determine required parameter relationships, expected return values, or side effects, making correct invocation unlikely.

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?

With 15 parameters and only 7% schema description coverage, the description needed to compensate but adds no meaningful parameter guidance. It does not clarify required title/menus semantics or how type, object, object_id, and url interact. The only hint, dry-run, merely repeats the schema's own description.

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 a specific verb and resource: 'Create classic menu item.' It clearly identifies this as a creation operation for menu items, which distinguishes it from menu, post, or widget tools. However, the 'classic' qualifier is ambiguous and no explicit differentiation from sibling menu-item tools is provided.

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 like wp_update_menu_item or wp_delete_menu_item. It does not mention prerequisites such as an existing menu, nor contexts where dry-run should be preferred.

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