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

Annotations cover safety hints (non-read-only, open-world, non-idempotent), and the description adds value beyond them: writes must be enabled ('Writes-gated'), the transport is plugin-based, and the Xyle Connector v0.6.0+ version requirement is a concrete prerequisite an agent cannot get from annotations. It could go further on whether the previous content is recoverable/snapshotted.

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 sentences, front-loaded with the core action and its accepted input formats, then the alternative tool, then the operational constraints. No filler or repetition.

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 9-parameter mutation tool with no output schema, the description plus schema covers what is needed: what gets overwritten, the two content formats, the lighter-weight alternative, write-gating, and the connector version. Nothing material an agent needs in order to invoke it correctly is missing.

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 100%, so the schema already documents all nine parameters (including the shape of `sections`/`atomic` and the purpose of `dry_run`). The description only adds the cross-reference that the `sections` spec matches `wp_create_page`; that is useful but marginal, so the baseline 3 applies.

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?

Specific verb + resource + scope: it replaces the template's *whole* Elementor content, and it states the two accepted input shapes (native `sections` spec or raw `elementor_data`). It explicitly distinguishes itself from the sibling `wp_patch_template`, so an agent can route without opening either schema.

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?

Names the alternative and the condition that selects it: 'For small tweaks prefer wp_patch_template.' It also signals write-gating and connector version prerequisites. It stops short of spelling out when a full replacement is the right call versus wp_replace_section or wp_set_template_conditions, so it is clear context rather than exhaustive guidance.

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