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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is covered. The description adds meaningful behavior beyond that: atomicity of the write, ordered application of patches to a single fetched document, and the concurrency rationale. It stops short of describing failure/rollback behavior or return shape.

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?

Three tight sentences, front-loaded with the atomicity guarantee and the concurrency justification before the array-format caution. The inline enumeration of patch fields partially duplicates the schema, but it serves the array-vs-string warning, so little 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 bulk mutation with no output schema, the description covers atomicity, ordering, the concurrency motivation, and validation knobs are documented in the schema enums. Missing only return/rollback behavior and the item-count limits, which the schema supplies.

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, but the description adds real value: the explicit warning that `patches` must be a real JSON array rather than a stringified one, plus the per-item patch field shape and the deferral to patch_site_node's rules for patch semantics.

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) with explicit scope (atomic write) and differentiates from the single-patch sibling by naming patch_site_node and noting that parallel single patches lose updates. An agent can distinguish this 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 tool over repeated single patches (lost updates under parallelism) and defers patch semantics to patch_site_node. It does not state explicit when-not conditions or limits (e.g. 1000-item cap is only in schema), so it falls short of full routing guidance.

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