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

Goes well beyond the annotations by naming the required capability (edit_theme_options), the not-found error behavior for unknown menus, item ordering ('in menu order'), and the exact returned shape including parent semantics (0 at top level). Annotations already cover read-only/idempotent safety, so this added permission and error detail is substantive surplus context.

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?

Five short sentences, front-loaded with what is returned, then shape, then permissions, then errors and discovery. Every sentence carries distinct operational information with no filler.

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?

No output schema exists, and the description compensates by enumerating the returned menu and item fields and their ordering. Combined with permission and error notes, an agent has everything needed to call and interpret this tool.

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 100% and the schema already says the menu parameter accepts 'id, slug or name, as wp_list_menus returns them'. The description adds no format or resolution details beyond that, so the baseline of 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 navigation menu with its items, in menu order') and distinguishes itself from the plural sibling wp_list_menus by returning a single menu plus its items. An agent can tell it apart from wp_list_menus without consulting the 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?

Points to wp_list_menus as the way to discover valid menu identifiers and warns that an unknown menu yields a not-found error, which shapes correct invocation. It does not state explicit exclusions, but the single-vs-list split with the sibling is clear enough for correct routing.

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