wordpress_update_menu_item

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

No annotations provided, and the description only states it updates. It does not disclose whether updates are partial or full, any destructive behavior, required permissions, or side effects. For a mutation tool, this lacks necessary transparency.

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 sentence of moderate length. It is concise but under-informative; not enough detail to compensate for brevity. Could be more structured by separating purpose and parameter hints.

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's complexity (two parameters, one a freeform object, no output schema, many siblings), the description is incomplete. It fails to convey validation rules, response behavior, or typical use cases, making it hard for the agent to use 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%, yet the description only vaguely hints at possible keys (title, URL, order) for the 'updates' object. It does not specify the structure, allowed fields, or constraints of the object, leaving the agent to guess. The itemId parameter is merely named with no further context.

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 the resource 'menu item', and provides examples of updatable fields (title, URL, order). It effectively distinguishes from sibling tools like create_menu_item, delete_menu_item, and get_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?

No guidance on when to use this tool versus alternatives. Among many update tools in the server, there is no mention of prerequisites, context, or exclusions. The agent receives no help in deciding between wordpress_update_menu_item and similar update tools.

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