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

Goes well beyond the annotations: discloses that no undo point is recorded (critical given wp_undo exists), that duplicates are created on repeat calls, that disallowed URL schemes (javascript:, data:) are refused, and that edit_theme_options is required. These are exactly the failure modes an agent could not infer from destructiveHint/idempotentHint alone.

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 front-loaded paragraph that leads with the action and its two modes before consequences and caveats. It is dense and slightly run-on, and the closing AlphaBridge forwarding sentence is scoping context rather than tool behavior, but nothing is redundant.

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?

A six-parameter mutation tool with no output schema, and the description compensates by naming the return shape ("added and item_id") plus permissions, duplication behavior, and undo absence. An agent has everything needed to call it correctly and anticipate the outcome.

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% and every one of the six parameters is already documented in the schema. The description reinforces the object_id/url precedence but adds no syntax, default, or format detail the schema does not already carry, so the baseline 3 applies.

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?

Specific verb plus resource ("Add a published item to a navigation menu") with the two operating modes spelled out: a content link when object_id is given, otherwise a custom link to url. An agent can distinguish it from wp_create_menu (creates the menu itself) and wp_delete_menu_item (removes items) without opening any schema.

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 names the removal counterpart (wp_delete_menu_item) and the capability prerequisite (edit_theme_options), and clarifies the object_id-vs-url selection rule. It does not explicitly state when to reach for wp_create_menu or wp_get_menu first, so it stops short of full when/when-not framing.

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