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

Annotations already flag destructive=true, non-idempotent, open-world, but the description adds substantial context beyond them: server-side reading of every text field, HTML preservation, application via the validated patch path, and a credit model where dry_run previews are free while real apply debits credits. These are exactly the behavioral traits an agent needs before invoking a destructive mutation.

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?

The core purpose is front-loaded in the first clause, followed by examples, mechanics, and cost guidance in a logical order. It is dense with em-dash clause stacking but every sentence carries actionable information, so almost nothing is wasted.

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 mutation with no output schema, the definition covers scope, mechanics, cost behavior, and the dry-run workflow thoroughly. It does not describe what a real (non-dry-run) apply returns or how to verify the result, a minor gap given the absence of an output schema.

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; the description slightly exceeds it by reinforcing that dry_run is the preview-plus-cost-estimate path and that instruction is a high-level intent rather than a literal string. It stops short of adding new semantics not already in the schema, so it is a modest addition over the structured fields.

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?

The description names a specific verb (transform) and resource (a page's text) driven by a high-level instruction, with concrete examples ('respecialize this urology page to pulmonology'). It explicitly distinguishes itself from the sibling wp_patch_template for header/footer/single-template edits, so an agent can route without opening a 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?

It states when to use it ('best for making a cloned page genuinely about a different topic'), a mandatory workflow step ('use dry_run=true FIRST'), and names the alternative (wp_patch_template) with the condition that selects it. When-to-use, when-not, and alternatives are all covered.

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