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

Goes well beyond annotations by disclosing the required capability (edit_theme_options), the exact return shape (a 'menus' collection with id, name, slug, count), and the connection scoping ('the one site this connection reaches'). Since annotations already declare read-only/idempotent, the auth and return-shape details are the value-add.

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 with the action and returned fields front-loaded, followed by auth and routing context. Every clause carries information an agent needs; nothing is repeated from structured fields.

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?

For a zero-parameter, read-only lister with no output schema, the description supplies the returned field names, the auth prerequisite, and the single-site scoping — everything needed to select and call it correctly.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. The description correctly implies no filtering or selection options exist.

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 (list) and resource (navigation menus) with explicit scope ('all at once') and enumerates the returned fields (id, name, slug, count). It is unambiguously distinguishable from wp_get_menu, which is named as the tool for a single menu's items.

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?

Clearly routes the agent: use this to get all menus in one call, and use wp_get_menu for the items of one menu. It does not add explicit exclusions for adjacent write tools like wp_create_menu or wp_get_menu edge cases, so it falls just short of the full when/when-not bar.

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