Write raw Elementor data

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 still adds real behavioral context — that the previous tree is snapshotted automatically and that a confirm:"overwrite" token is gated in — which is more than the annotations alone convey. It stops short of saying how to recover or whether the snapshot is prunable.

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 short sentences, front-loaded with the destructive replace, then the alternative, then the constraints. Every sentence earns its place and nothing is padded.

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, no-output-schema write tool, the definition covers purpose, alternative, gating token, and the safety net. Missing only recovery pointers (wp_el_restore / wp_el_snapshots) that would fully close the loop on an overwrite operation.

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 description coverage is 50%, so the description has to carry some weight, and it does: it explains the exact confirm value and reveals the automatic snapshot behavior behind the snapshot parameter, plus frames what data must contain (valid Elementor JSON). post_id is left unexplained, but that is self-evident.

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: "Replace the whole Elementor tree for a page." It also implicitly distinguishes itself from wp_el_build by naming it and by scoping the tool to already-valid Elementor JSON, so an agent can tell the two apart without opening schemas.

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?

Explicitly routes the agent: "Use wp_el_build for authored pages and this only when you already have valid Elementor JSON." That is a clear when-to-use plus a named alternative, leaving almost nothing to inference.

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