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

Annotations already cover read-only/non-destructive, but the description adds real behavioral context: it notes the server marks it read-only so it runs immediately, that only published items are returned, and the default page size. The long field-by-field account of the response shape compensates for the absent output schema, though it stops short of saying how to detect the last page or whether a total count is returned.

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 key scoping sentence is front-loaded, which is good, but the remainder is one enormous run-on sentence enumerating a dozen fields, which is hard to scan. The content is mostly warranted given no output schema, yet it could have been structured as a short list rather than dense prose.

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, describing every returned field is genuinely necessary and is done thoroughly, and the read-only/pagination context is present. The main gap is pagination termination and how menu_id is sourced, which an agent would need to call this reliably across multiple pages.

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%, so the schema already documents page, per_page, site_id and menu_id. The description's only added parameter meaning is the '100 per page by default' pagination note, which largely restates the per_page default; menu_id's provenance is never explained.

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 opening sentence gives a specific verb and resource ("Lists all items in a WordPress navigation menu") plus scope (published items, 100 per page). It implicitly distinguishes itself from menu-level siblings like wp_list_menus / wp_get_menus by being about items, but it never names the closest sibling (royal-mcp__wp_get_menu_items) explicitly.

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 statement of when to use this versus alternatives such as wp_get_menu_items, wp_get_menu, or wp_reorder_menu_items, and no note that menu_id must first be obtained from a menu-listing call. Usage is only inferable from the tool name and the 'published items' scope.

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