wordpress_update_menu_item

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

No annotations are provided, so the description carries the full burden. While it lists mutable fields, it fails to disclose whether updates are partial/optional (implied by defaults but not stated), idempotent, or what the return value contains. No safety warnings or permission requirements are mentioned.

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 brief and front-loaded with the action verb. However, the '[UNIFIED]' prefix adds noise without value, and the second sentence could be more specific about parameter requirements.

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 6 parameters with 0% schema coverage and no output schema or annotations, the description is insufficient. It fails to document the required site/item_id parameters, doesn't explain the update behavior, and provides no return value information.

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 description coverage, the description partially compensates by listing four of the six parameters (title, URL, parent, menu_order). However, it omits the two required parameters (site, item_id) and provides no semantic detail on data formats (e.g., whether 'parent' expects an ID or name, or what 'menu_order' represents).

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 verb (Update) and resource (menu item), and lists the specific fields that can be modified. However, it does not explicitly differentiate from sibling tools like wordpress_create_menu_item or wordpress_list_menu_items.

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?

There is no guidance on when to use this tool versus alternatives (e.g., when to use wordpress_create_menu_item instead), no mention of prerequisites like requiring a valid item_id, and no indication of partial vs. full update semantics.

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