List navigation menus

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by warning that FSE themes may not use classic menus and pointing to the correct fallback. This goes beyond what annotations alone convey.

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?

Two sentences with no filler: the main purpose is stated first, then a brief and relevant caveat about FSE themes. Every sentence contributes meaningful information.

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 read-only list tool with one optional parameter and no output schema, the description explains what is returned (menus and their theme locations) and when results may differ (FSE themes). The note about list_content completes the picture by routing the agent to the correct tool when needed.

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 schema fully documents the single optional site_id parameter, including behavior with one vs. multiple configured sites and a pointer to list_sites for valid ids. The description adds nothing about parameters, but with 100% schema coverage it does not need to. Baseline 3 is appropriate.

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 description uses a specific verb and resource: 'List the site's navigation menus and which theme locations they are assigned to.' It clearly distinguishes itself from sibling tools like get_menu, create_menu, and delete_menu by indicating it lists all menus rather than acting on one. The added note about full-site-editing themes further sharpens the purpose.

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?

The description explicitly states when to use an alternative: for block themes using navigation blocks, list_content with type 'wp_navigation' is recommended. This gives the agent a clear conditional rule for choosing between this tool and a sibling. No other guidance is needed for such a straightforward list operation.

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