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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds value by stating what the call returns (the location→menu assignment mapping), which matters because there is no output schema. It does not mention behavior for unassigned locations or sites without a nav menu, leaving a mild gap.

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 short sentences with zero padding; the scope statement is front-loaded and the return-content sentence follows immediately. Every clause earns its place.

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 one-optional-parameter, read-only listing tool with annotations and no output schema, the description covers the essentials: what is listed and roughly what comes back. It falls short only on how unassigned locations appear in the result.

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 description coverage is 100% for the single optional site_id parameter, so the schema already documents its meaning. The description adds nothing about the parameter, so the baseline 3 is the right call.

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 — listing theme-registered menu locations — and clarifies the scope with concrete examples ("primary", "footer", "mobile"). The second sentence states what the result contains (the menu assigned to each location), which implicitly separates it from siblings like wp_list_menus, though no sibling is named explicitly.

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 gives no when-to-use guidance, no prerequisites (e.g. requiring a connected site / site_id), and never mentions the obvious alternatives wp_list_menus, wp_get_menu, or wp_list_menu_items. Usage must be inferred entirely from the purpose sentence.

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