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

Annotations already declare read-only/idempotent/non-destructive, and the description still adds substantial context: returned values are plain JSON, dynamic tags take the shape `{ name, settings }`, only keys under `properties` are accepted, styling must go into the `style` CSS input, and unsupported types produce a named error. That is real behavioral disclosure rather than restating 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?

Dense but front-loaded: the definition opens with what is returned, then the discovery prerequisite, then the payoff/usage constraints. The closing Royally note about read-only execution is mildly redundant with the annotations, but every other sentence carries actionable information.

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?

There is no output schema, so the description carries the burden and does: it explains the return value (per-widget JSON Schema with defaults and nesting guidance), the expected downstream input shape, and the error case. An agent has everything needed to pick this tool and feed its output forward.

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 baseline would be 3, but the description adds meaning beyond the schema by constraining what counts as a valid `widget_type` (only registry identifiers returned by `list-widget-schemas`) and by explaining how the resolved settings should later be supplied to `build-composition.element_config` and `manage-elements.settings`.

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?

States a specific verb and resource: returns the JSON Schema for a single widget type's settings, including defaults and nesting guidance. It is immediately distinguishable from the sibling `elementor-list-widget-schemas`, which is named as the bulk-discovery counterpart.

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?

Gives an explicit prerequisite workflow: call `elementor/list-widget-schemas` with `summary=true` first to discover valid `widget_type` values. It also names the failure path (types not returned there fail with `elementor_v3_not_supported`) and the fallback (edit directly in the Elementor editor).

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