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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false. The description adds value beyond them by disclosing atomicity, that patches are "applied in order to one fetched document," and the merge semantics (namespaced objects deep-merge, strings/arrays replace, Image src + content together, no children). It could be clearer that unsetProps/unsetClasses destroy data, but the behavioral surface is well covered.

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 tightly packed sentences: purpose + rationale first, then the field enumeration and merge rules. Front-loaded and free of filler, though the second sentence is dense enough that it reads more like reference notes than prose.

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 bulk mutation tool with no output schema, the description covers the essentials an agent needs: atomicity, ordering, and the merge/replace rules that determine the write outcome. Combined with the fully documented schema and mutation annotations, nothing material 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 description coverage is 100%, so the baseline is 3. The description exceeds that by explaining the patch object shape and, more usefully, the semantics of each field (deep-merge vs replace, single-document ordering, "no children" constraint) that the schema only names. It adds real meaning over the field list.

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 ("Apply many node patches") and immediately distinguishes itself from the single-node sibling by contrasting its atomic bulk write with "parallel single patches [that] lose updates." An agent can tell this apart from patch_site_node without opening either 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 a clear reason to prefer this over patch_site_node (atomicity; parallel single patches lose updates), which functions as an implicit when-to-use rule. It stops short of explicit when-not-to-use guidance, but the routing signal is strong and unambiguous.

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