wp_list_menus

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

Explicitly states 'Read-only', which is a behavioral guarantee. It also discloses a limitation (does not fetch menu items) and a prerequisite (REST transport). Since no annotations are provided, the description carries the full burden and does so effectively.

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 description is concise, consisting of exactly four short sentences with clear structure. It covers the core purpose, usage pointers, and constraints without any fluff or redundancy.

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?

Given the low complexity of the tool (single read-only operation), the description provides adequate context for typical use, linking it to the menu-item workflow and transport requirements. It lacks parameter explanation, which is a minor gap but not critical for the main scenario.

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 only parameter, 'install', has no description in the schema and is not explained in the tool description. Schema coverage is 0%, and the description does not compensate, leaving the agent without information about what value to pass.

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 clearly states the verb 'List' and the resource 'a site's navigation menus', and explicitly enumerates the returned fields (id, name, slug, theme locations). It distinguishes itself from sibling tools by indicating this is the starting point before adding menu 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?

Provides explicit guidance on when to use this tool ('Start here'), notes that menu items are not fetched (so another tool is needed for that), and mentions the REST transport requirement, which is a key usage constraint.

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