wordpress_assign_menu_to_location

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

With no annotations present, the description carries the full burden of behavioral disclosure. 'Assign a menu to a theme location' implies a write operation but fails to disclose whether an existing menu at that location is replaced, what permissions are required, or what the return value is.

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 a single, front-loaded sentence with zero filler words. Every word earns its place, and the structure is ideal for quick parsing by an agent.

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?

Although the tool is simple (2 required params, no output schema), the absence of annotations and the 0% parameter coverage leave important gaps: the agent cannot know whether assigning overwrites an existing location assignment, what the response format is, or whether any preconditions apply.

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 0%, so the description must compensate for the bare parameter names. It adds minimal context by identifying menuId as the menu and location as a theme location, but it does not explain valid location values, how to obtain a menuId, or any format/relationship details.

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 'Assign a menu to a theme location' uses a specific verb (assign) and identifies both the object (menu) and target (theme location), making the core action clear. However, it does not explicitly call out sibling tools like wordpress_get_menu_locations or wordpress_create_menu, leaving differentiation implicit rather than stated.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., menu must exist, location must be registered), when to prefer it over creating a new menu, or any exclusions, so the agent receives no contextual direction.

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