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

Beyond the annotations, the description explains both return shapes, how returned schema values should be used in `build-composition.element_config` and `manage-elements.settings`, and that only keys under `properties` are accepted with visual styling going in the `style` input. It also discloses the manual-edit limitation for absent widget types.

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 front-loaded with purpose and then organized by mode, usage, and integration details. It is mostly efficient, though the closing note about the server marking it read-only largely repeats annotation information and could be trimmed.

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?

Given there is no output schema, the description fully explains the two possible return shapes and how the returned schemas should be consumed. It also covers discovery order, alternatives, and the limitation for widget types not present in the list.

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 parameter definitions already carry most meaning. The description still adds useful mode semantics by explaining that default mode returns a map and `summary=true` returns a discovery array, which helps an agent understand the practical effect of the boolean parameter.

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 and resource: it returns widget information/schemas for every configurable widget type. It also clearly distinguishes the default full-schema mode from the summary/discovery mode, and explicitly names `elementor/get-widget-schema` as the alternative when only one widget type is needed.

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 routing guidance: prefer `elementor/get-widget-schema` for a single widget, and use `summary=true` first when discovering widget types or before building compositions. It also notes that types absent from the list must be edited manually, which is a clear boundary condition.

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