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

Annotations declare the safety profile (readOnly=false, destructive=false, idempotent=false, openWorld=true), but the description adds substantial context beyond them: server-side execution in ONE call, that it returns per-variant {post_id, title, replacements_made} and never page content, that each variant is a reviewable draft, and that it is round-trip validated and write-gated.

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?

Dense but front-loaded: the core behavior comes first, then the rationale, then the return shape, then the sibling pointer. Every sentence carries distinct information, though the description is on the longer side for a three-parameter tool.

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, the description compensates by spelling out the return shape ({post_id, title, replacements_made}, never page content) and the draft/write-gated semantics. Nothing needed 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 coverage is 100%, so baseline is 3. The description goes further by framing 'variants' as a compact list replacing full page payloads and describing the shape of the returned replacements_made, tying the parameter to its purpose rather than just restating it.

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 precise verb and resource ('Clone a source Elementor page into N variants, applying each variant's find/replace to its clone') and immediately distinguishes itself from the nearest siblings by contrasting the N-clone-calls-plus-N-patches alternative. An agent can identify the tool's role 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?

Explicitly names the pattern it targets ('one source page -> many near-identical variants with swapped terminology') and names the alternative and its selection condition ('For an INTELLIGENT transform beyond literal swaps... run assist_transform_page on a clone instead'). Both when-to-use and when-to-choose-something-else are present.

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