wordpress_update_navigation

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

Describes it as an update operation that writes post_content and other fields. No annotations, so description carries burden. Reveals mutation but could mention side effects or permission requirements.

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?

Two sentences, front-loaded with purpose and scope. '[UNIFIED]' is minor noise, but overall efficient.

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?

Covers purpose and use case, but lacks parameter details, return value, error conditions, and prerequisites. Adequate for simple updates but incomplete for complex scenarios.

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 0%. The description loosely lists 'title/status/slug/meta' but provides no detail on format, defaults, or meaning per parameter. Minimal added value 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?

Clearly states it updates a wp_navigation post (block-theme menu) and lists writable fields. Distinguishes from get/list siblings by focusing on mutation and fixing hrefs.

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?

Explicitly recommends using this tool to fix navigation-link hrefs set in Site Editor, providing a concrete scenario. No explicit when-not or alternative tools, but the context is clear enough.

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