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

The annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds genuinely new operational context ('no site needed'), telling the agent no WordPress connection is required for this lookup. 'Read-only' merely restates the annotation, and the non-idempotent annotation is left unexplained, keeping it out of 5 territory.

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?

Three tight sentences: purpose first, then the mandatory call order, then the read-only/no-site caveat. No filler, and the most decision-relevant information (what it returns, when to call it) is front-loaded.

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 no output schema, the description usefully sketches the return content (supported style fields plus their raw setting keys) and an example. Given the large sibling set, it could do slightly more to disambiguate itself from wp_widget_controls/wp_widget_schema, but nothing needed to invoke it correctly is missing.

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 the widget_type description already documents 'icon-box', 'heading', 'button', 'container' and 'all'. The description adds no elaboration on parameter values or filtering beyond what the schema says, 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?

The description states a specific verb+resource: it returns which style fields a widget type supports and the raw Elementor setting keys they map to, with a concrete example (icon-box colour -> 'title_color'). This is distinguishable from lookalike siblings such as wp_widget_controls, wp_widget_schema and assist_widget_keys, which deal with controls/schema rather than style-key mapping.

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?

It gives explicit sequencing — 'Call this BEFORE styling a widget' — and names the downstream tool and payload shape (wp_patch_page as {node_id, style:{...}}). It does not state when NOT to use it or how it differs from wp_widget_controls/wp_widget_schema, so it stops short of full routing guidance.

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