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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so 'read-only, runs straight away' largely restates them. The description does add genuinely new behavioral context: post_type/taxonomy items inherit the link of their target, so only custom items' urls are mutable — a non-obvious constraint an agent would not get from the schema.

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?

Purpose is front-loaded in the first clause and the field enumeration is informative rather than padding. The trailing '(site: ...)' and 'Through Royally: read-only, runs straight away' are boilerplate that add little, keeping it short of 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 description usefully documents the returned field set, and annotations cover the safety profile for this read-only tool. The remaining gap is guidance on sourcing menu_id, which the description should supply given the undocumented required parameter.

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 coverage is only 50%: site_id is fully described with an enum, but menu_id is a bare integer with no description. The description says 'items of a menu' but never explains that menu_id is the menu term ID nor how to retrieve it, so it fails to compensate for the coverage gap on the one required parameter.

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 the items of a menu') and enumerates the returned fields (id, title, url, parent, order, type, object, object_id, target), which distinguishes it from the sibling wp_get_menus that lists menus themselves. An agent can tell what this returns without opening any 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?

Usage is implied by the required menu_id, but the description never says to first call wp_get_menus to obtain a menu_id, nor does it state when to prefer this over mcp-easy-ai__wp_list_menu_items or the generic wp_rest_read. The only routing hint is the note about editing custom item urls, which points implicitly at wp_update_menu_item.

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