Build an Elementor page from a spec

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is known. The description adds useful workflow context (dry_run gate, dry_run-first advice), but never states what an overwrite actually destroys on an existing page or whether auth is needed, so it only partially earns credit beyond the 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?

Front-loaded with the core action, followed by the dry_run gate, then post_id behavior, then setting-key examples. Every sentence is useful; only the widget-key examples edge toward verbosity.

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 deeply nested 5-param tool with no output schema, the description covers the spec shape, the dry_run workflow, and new-vs-existing page selection. It is nearly complete, with only the destructive effect of overwriting an existing page and the return shape left implied.

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?

With 60% schema coverage, the description compensates well: it explains the spec's section/column/widget shape and gives concrete Elementor setting-key examples (heading {title, header_size}, button {text, link.url}), which the schema cannot convey. The post_id omission behavior is also clarified, though confirm='overwrite' is left to the schema.

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 (convert spec into Elementor data) plus the conditional write behavior, and the resource is clearly an Elementor page. This distinguishes it from read/write siblings like wp_el_get and wp_el_set, though it does not explicitly name the closest sibling (wp_el_set) as an alternative.

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 clear operating context: the write only happens unless dry_run, post_id omission creates a new page, and it recommends always inspecting the dry_run output first. It lacks explicit when-not/alternative routing against wp_el_set or wp_content_create, so it stops short of full 5-level guidance.

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