wordpress_create_menu_item

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

No annotations provided, so description carries full burden. Mentions supported link types but omits side effects, error behavior when menu_id is invalid, whether operation is idempotent, or return value structure.

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 purpose front-loaded. The '[UNIFIED]' prefix is noise/metadata, but core content is efficiently stated without redundancy.

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 6-parameter write operation with no output schema or annotations. Missing critical documentation for half the parameters and lacks behavioral details expected for a creation tool.

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 0% schema coverage, description hints at relationship between type/object_id/url parameters (linking logic) but fails to document site, menu_id, parent (for nesting), or the required title parameter which appears in required array but not properties.

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 'Add a new item to a menu' with specific verb and resource. It distinguishes from sibling tool wordpress_create_menu by focusing on 'item' within existing menus rather than creating the menu container itself.

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?

Lists supported link types (posts, pages, categories, custom URLs) providing usage context, but lacks explicit prerequisites (requires existing menu_id) or guidance on when to use wordpress_update_menu_item instead.

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