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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds non-redundant context: it enumerates the exact returned fields, which matters because there is no output schema. 'Read-only, runs straight away' largely restates the annotations, so it is not a 5.

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?

Front-loaded with the purpose and lookup key, and the field list is compact but informative. The trailing parenthetical site hint and 'Through Royally: read-only, runs straight away' pad the sentence without adding much, keeping it from a 5.

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?

With no output schema, the returned-field enumeration is exactly the information an agent needs to consume the result, and the read-before-update hint covers the workflow. Error behavior for a missing or invalid menu item ID is the one notable omission.

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 100%: both menu_item_id and the site_id enum are documented in the schema itself. The description only repeats 'by ID' and does not clarify format, range, or error behavior for an invalid ID, so it adds little beyond the schema. Baseline 3 applies.

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 (get one menu item) plus the lookup key (by ID), and implicitly contrasts with the sibling list tool wp_get_menu_items by naming it as the field source. An agent can tell it apart from wp_get_menus, wp_get_menu_items and wp_update_menu_item without opening a schema.

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?

'Use it before wp_update_menu_item' gives an explicit read-before-mutate workflow and names the tool it pairs with. It stops short of saying when not to use it (e.g. when listing all items, use wp_get_menu_items), so it falls just short of a full when/when-not statement.

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