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

Goes well beyond the annotations by disclosing that V3 settings merge raw without schema validation, that CSS is wrapped in `selector { ... }` and stored in V3's custom_css, that per-op partial success is supported, and that the whole batch is saved once. It also surfaces the Royally approval gate and the explicit 'no undo' limitation, which is critical for a destructive, non-idempotent tool.

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 opening clause front-loads scope well, but the body is a dense wall of V3 edge cases and the text is truncated mid-word ('native-shape intera…'), which costs the reader information. The trailing Royally approval and no-undo boilerplate is useful but appended rather than integrated.

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?

For a destructive, open-world mutation tool with no output schema, the description covers the important ground: allowed targets, V3 limits, merge semantics, per-op error behavior, and the approval/undo constraints. The only real gap is the truncated sentence about interactions and native shapes, which leaves that parameter's contract incomplete.

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 67%, and the description adds real meaning on top of it: breakpoints use @media (--mobile) syntax and explicitly NOT pixel queries, classes map to V3's space-separated _css_classes, style maps to custom_css, and new_parent_id may reference V3 or V4 containers. Some of this overlaps the schema's own field descriptions, but the V3 storage mapping and the pseudo-state/breakpoint caveat are genuinely additive.

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: bulk surgical edits on V4 atomic elements in a document, capped at 50 operations on a single tree saved once. It also explicitly enumerates which element types are valid targets, which is more than most siblings offer. It does not, however, differentiate itself from adjacent Elementor siblings such as elementor-build-composition or elementor-create-page.

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 a clear when-not condition: V3 targets outside the closed allowlist return elementor_v3_not_supported and must be edited directly in the Elementor editor. It also points to elementor/list-widget-schemas for the allowlist and warns that custom_css requires Elementor Pro. It does not route the agent between this and other editing tools (e.g., build-composition) for creating new content.

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