wordpress_create_menu_item

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It merely states 'Add an item,' implying a write operation, but does not disclose whether an existing menu is required, how the 'menus' parameter is used, whether the operation is idempotent, or what response to expect. This is minimal and lacks meaningful behavioral detail.

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 a single, concise sentence with no filler, but it is too under-specified to be genuinely helpful. It is not tautological, but it sacrifices essential detail for brevity. The structure is acceptable, but the content is minimal.

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?

Given the tool has two parameters, no annotations, no output schema, and a 0% schema description coverage, the one-sentence description is completely inadequate. It does not explain the parameters, the required input format, or the expected outcome, leaving the agent without sufficient context to call the tool 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 0%, and the description does not explain the two parameters ('menus' and 'title'). The agent cannot infer that 'menus' likely refers to a menu ID, nor how 'title' is used. The description completely fails to compensate for the undocumented schema, making parameter usage unclear.

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 action ('Add') and resource ('an item to a navigation menu'), using a specific verb+resource pattern. It implicitly distinguishes itself from siblings like wordpress_create_menu (creating the menu itself) and wordpress_update_menu_item (modifying an existing item). The purpose is unambiguous.

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 is provided on when to use this tool versus alternatives such as wordpress_create_menu or wordpress_update_menu_item. The description does not mention any prerequisites, exclusions, or alternative conditions, leaving the agent without context for selection.

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