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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is fully covered. The description adds the useful detail that item counts and theme-location assignments are included in the result, but says nothing about ordering, pagination, or emptiness handling.

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?

A single front-loaded sentence with the verb, scope, and return payload packed in without a wasted word. Nothing is buried or repeated.

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-parameter read-only list tool with full schema coverage and complete annotations, the description covers purpose and output shape, which is close to everything an agent needs. The only shortfall is the missing differentiation from similarly named sibling list tools.

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?

Only one parameter, site_id, and the schema documents it at 100% coverage including the explicit "call list_sites first; do not use a URL or post ID" warning. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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 ("Lists all registered navigation menus") plus the fields returned (item counts, theme locations), so the agent knows exactly what comes back. It does not distinguish itself from the sibling tools wp_list_navigation_menus or wp_list_menu_locations, leaving the agent to guess which lister to call.

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?

Usage is only implied by the verb "Lists" – there is no explicit statement of when to choose this over wp_list_navigation_menus or wp_list_menu_locations, and no prerequisites or exclusions beyond what the schema mandates. Adequate but leaves the sibling disambiguation entirely to inference.

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