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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known; the description adds the crucial operational context that this is a full replacement requiring prior read and human approval. It stops short of spelling out that rules omitted from the list are deleted, though 'complete' and the schema's '[] to clear all rules' imply it.

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?

Two sentences, zero waste, with the replacement scope front-loaded and the prerequisite workflow following immediately. Every clause carries actionable information.

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, idempotent mutation with no output schema, the description supplies the missing pieces: read-before-write, ID preservation, and approval gating. An agent has everything needed to invoke it safely and correctly.

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 all three parameters and nested rule fields are already documented, including ID preservation and the empty-array clearing behavior. The description reinforces the ID-preservation rule but adds no syntax or format detail beyond the schema, so 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?

States a specific verb (Replace) and resource (one receptionist's complete Lead Alert setup), and enumerates the scope: enabled state plus full ordered rule list. It is clearly distinguishable from the sibling lead_alerts_get, which it explicitly references as the read counterpart.

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 an explicit workflow: call lead_alerts_get first, preserve existing rule IDs, show the exact resulting setup, and obtain explicit approval before calling. This is a when-and-how directive that leaves nothing to inference.

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