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

Goes well beyond the annotations: write-gated execution, dry_run before/after diff, and a detailed EFFECT CHECK contract explaining that applied:true is insufficient and effective:false means the widget ignored the key with the stored value showing what landed. It also discloses the verification boundary ('verifies stored data, not final render') and points to render_screenshot. This is exactly the behavioral context annotations cannot convey.

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?

Long, but structurally disciplined — lead pitch first, then per-op-type sections, then the effect-check caveat, then the sibling fallback. Dense compound sentences pack multiple facts; a few parentheticals are tightly compressed, but for a multi-builder patch tool almost every line carries operational weight.

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?

There is no output schema, so the description must describe return behavior — and it does, explaining the effective:true/false flags, effective_count/ineffective_count, and the stored value, plus the note that ops=[] performs a V4 text type-repair pass. Nothing an agent needs to call this 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 coverage is already 100%, but the description adds substantial meaning: it enumerates the two op shapes (CONTENT {node_id, field, new_value}, STYLE {node_id, style:{...}}), the valid field vocabulary, object new_value forms like {"unit":"px","size":18}, the Gutenberg 'attrs.<dotted.key>' convention with null-delete semantics, and the tabs relabel/order form. Far above the baseline 3 for full-coverage schemas.

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 — 'surgically edit an Elementor page by element id' — and explicitly contrasts itself with wp_update_page ('which rewrites the WHOLE page'). An agent can distinguish this from the many wp_* siblings without opening any 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?

Gives explicit when-to-use: send only the elements you're changing, use dry_run to preview, call wp_style_keys first for widget support. It also names the alternative and its condition ('Use wp_update_page only for full redesigns / adding new sections') and lists refusal conditions (style ops on Gutenberg, html op on a parent plus child edit).

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