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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: it never states that assigning a menu to an occupied location displaces or overwrites the previously assigned menu, nor that the theme must support the location. For a destructive, non-idempotent operation this is a meaningful gap, though the annotations carry the core warning.

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 short sentence, front-loaded with the verb and resource, with zero redundant wording. Its brevity is efficient but borders on under-specification rather than being genuinely economical with 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?

With three required parameters, full schema descriptions, and annotations covering mutability and destructiveness, the minimum needed to call the tool is present. What is missing is the consequence of the call: an agent cannot tell from the description what happens to a menu already assigned to that location, which matters given destructiveHint=true and idempotentHint=false.

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%, and the schema already explains menu_id, site_id (including the instruction to call list_sites first and not to use a URL or post ID), and the location slug. The description adds no meaning beyond the schema, which is the expected baseline when the schema does the heavy lifting.

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 states a specific verb ('assigns'), a specific resource ('a navigation menu'), and a target ('a theme menu location'), which is enough for an agent to distinguish this from sibling tools such as wp_list_menu_locations or wp_update_navigation_menu. It stops short of explicitly naming those siblings or the relationship between them, so it is clear but not fully differentiated.

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?

There is no guidance on when to use this tool versus alternatives. Nothing tells the agent how this differs from wp_update_navigation_menu or that wp_list_menu_locations should be called first to discover valid location slugs, and there are no stated preconditions or exclusions.

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