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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so 'Read-only' in the description is largely redundant. The description does add genuinely new context beyond the annotations: it requires plugin transport and Xyle Connector v0.6.0+, which tells the agent a compatibility precondition exists, but it omits what happens when that requirement is unmet (error vs empty result).

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 short sentences with the purpose front-loaded, followed by the safety posture and the runtime prerequisite. Nothing is padded and each sentence carries a distinct role, making it easy to scan.

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 listing tool with no output schema, the description is nearly sufficient: it names what is returned (menus with their items plus theme menu locations) so the agent can anticipate the payload. It stops short of covering failure/availability behavior when the plugin or required version is absent.

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 schema description coverage is 100%, so the schema already carries the semantics; the baseline is 3. The description adds no constraints, format, or scoping detail about site_id beyond what the schema states.

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 ('List WordPress nav menus') and even enumerates the contents returned (menus with items plus the theme's registered menu locations). However, it never names or distinguishes itself from close siblings such as wp_list_menu_locations or wp_list_pages, so an agent must infer the boundary from the schema alone.

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: the agent can infer this is the tool for enumerating nav menus, and 'Read-only' signals a safe inspection call. There is no explicit when-to-use, no exclusion, and no pointer to the sibling with which it overlaps (wp_list_menu_locations), leaving the agent to guess which listing tool to pick.

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