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

Annotations only declare readOnlyHint=false / destructiveHint=false; the description adds the traits that actually matter: all insertions land in one new draft version, the batch is all-or-nothing on a missing parent, colliding id, or bad after_id, and the cap is 50 per call. It further discloses the returned id_map, the slot-tagging validation behavior (unknown slot rejected with closest valid names, untagged content produces a warning), and the extra: {slot} convention for get_page(view: content).

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?

Structure is front-loaded and logical: what it does, insertion shape, structural-add use cases, copy_of alternative, cross-page collection case, safety versus patch_fixture, tagging, failure modes, limits. It is still dense and runs long for a tool description, and the doubled 'get_primitive_schema + get_primitive_schema' plus the unsupported node_json variant are sentences that don't earn their space.

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?

There is no output schema, yet the description still tells the agent what comes back (id_map for copies), what a rejection looks like and its three triggers, and the batch size ceiling — everything needed to call it correctly and to chain patch_nodes afterward. For a 2-parameter, atomic, mutation tool this is complete.

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?

At 50% schema coverage the description does real work: it explains position's three spellings, that parent_id may point anywhere in the fixture (pages + siteElements), and the copy_of-versus-node decision with the copy's exact-match/fresh-id semantics. It loses a point for describing an input shape the schema forbids — a single top-level `parent_id` + `node_json` — which would fail against this draft-07 schema's root `additionalProperties: false`, and for the garbled 'Use get_primitive_schema + get_primitive_schema'.

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 opens with a specific verb and resource ('Add many nodes to a site in ONE call, batched into one new draft version') and immediately names the sibling it supersedes for raw path-level edits (patch_fixture's JSON-Patch 'add'). It also splits the space between inserting new subtrees and cloning existing ones via copy_of, so an agent can distinguish this from add_section, add_page, or move_nodes 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?

When-to-use is spelled out with concrete scenarios (new section on a page, nav link, card in a grid, restoring a removed container), and when to switch to copy_of is given with its own trigger ('adding one more of something that already exists') plus a follow-up step (patch_nodes the copy's text via id_map). It even routes the cross-page collection case ('put my latest projects on the About page') to copy_of the collection-list with limit set, which is a non-obvious alternative an agent would otherwise get wrong.

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