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

Annotations already flag destructiveHint=true and non-idempotence; the description goes further by disclosing the credit cost, the round-trip-checked and write-gated write path, and the dry_run escape hatch. It also clarifies the division of labor (agent orchestrates; service reads, generates, writes), which is behavior an agent cannot infer from the schema.

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 verb and differentiator, then prerequisites and cost. The 'You orchestrate; XeoRank reads+generates+writes.' line is slightly rhetorical but does encode the responsibility split, so almost every sentence earns its place.

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?

With no output schema and a destructive, credit-metered write, the description covers the workflow, id sourcing, preview, gating, and cost. It does not spell out failure/rollback behavior or the write-enablement prerequisite implied by 'write-gated' (cf. wp_enable_writes), leaving a small gap for a mutation tool.

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 100%, so the baseline is 3, but the description adds real meaning: where node_id comes from (assist_page_digest), the natural-language register expected for instruction (with worked examples), and the preview semantics of dry_run. That is above the baseline without being exhaustive.

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+resource ('EDIT a page element') plus the key differentiator: intent-based rewriting with no HTML handling on the caller's side. It also names the mechanism (server-side read, small-model rewrite, validated patch) that separates it from sibling writers like wp_patch_page or wp_replace_section.

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 concrete prerequisite ('Get element ids from assist_page_digest'), a safe-preview path (dry_run=true), and the cost implication ('Costs Assist credits'). It stops short of an explicit when-not-to-use or a named alternative for direct HTML editing, so it is strong context without full routing guidance.

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