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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds real behavioral context beyond them: that an argument-less call returns classic menus plus block-theme navigation blocks, and that the result supplies the ids/paths needed for later editing.

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?

Three tight sentences, front-loaded with what the tool lists, then the discovery-first call pattern, then the follow-up modes. No filler or repetition of the title.

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?

An output schema exists so return values need not be spelled out, yet the description still states the useful shape (menus, locations, links). It omits any mention of site_url, which is the one gap for a zero-required-parameter 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 0%, so the description must carry the load, and it does for menu_id (classic menu links) and nav_id (navigation block links) and implicitly for their defaults via the no-argument call. Only site_url is left undefined, keeping it short of a 5.

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 (list navigation menus of a WordPress site) and enumerates the content returned: navbar, footer menus, theme locations, and inner links. It is clearly distinguishable from wordpress_edit_menu and other wordpress_* siblings by scope and intent.

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?

Gives an explicit call sequence: call with no arguments first to discover menus, then pass menu_id for a classic menu's links or nav_id for a navigation block's links. It doesn't name wordpress_edit_menu as the follow-up tool, and the site_url parameter's role is never addressed, so it is strong but not exhaustive.

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