Update Navigation Menu

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

Annotations provide idempotentHint=true, destructiveHint=false, and readOnlyHint=false. The description adds value by disclosing the 'Requires admin' permission and specifically noting that locations 'replaces existing' assignments—important behavioral detail not fully captured by the annotations.

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 concise and front-loads the core purpose in one sentence. The Args block is efficient, but it partially duplicates the schema and could be trimmed. Still, every sentence earns its place, including the admin requirement.

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 4-parameter tool with no output schema, the description covers the purpose, parameters, permission requirement, and the replacement behavior of locations. It lacks explicit side effects beyond the parameters, but given the idempotent and non-destructive hints, this is acceptable.

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 coverage is 100%, so the schema already documents each parameter. The description repeats the parameter list but adds the nuance that 'name' and 'locations' are optional and clarifies that locations replaces existing assignments, which is useful but not a major addition beyond the schema.

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 clearly states the tool's function: 'Rename a menu and/or change its theme-location assignments.' It uses a specific verb and resource, and distinguishes from sibling tools like wp_update_menu_item (menu items) and wp_create_menu/delete_menu.

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 implies when to use the tool (to rename a menu or change locations) but does not explicitly contrast it with alternatives or edge cases. It mentions 'Requires admin' as a prerequisite, but lacks direct 'when not to use' guidance.

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