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

Annotations only declare destructiveHint=true; the description adds far more: the operation is all-or-nothing with no partial saves, a rejected operation reports which one failed, batching is cost-neutral, and baseVersion triggers an optimistic-concurrency refusal instead of an overwrite. This is exactly the behavioral context an agent needs before a destructive write.

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?

Four sentences, front-loaded with the core action and scope, then atomicity, then batching guidance, then the concurrency parameter. No filler, no repetition of the title, and each sentence carries a distinct decision the caller must make.

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 21-variant batch-mutation tool with no output schema, the description covers atomicity, failure reporting and concurrency well. The main gap is the success path: it never says what comes back (e.g. a new version to feed the next call), which matters in a multi-call editing workflow where baseVersion must be threaded forward.

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 at top level is only 33%, but the nested operation schemas are well annotated. The description contributes real semantics the schema cannot express: operations are 'applied in order' and the whole list is atomic, which is essential for reasoning about dependency between ops. It adds nothing, however, about siteId or the 200-operation cap.

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 ('Change a Studio site') and enumerates the full scope it covers: pages, sections, nodes, per-breakpoint styles and components. It also distinguishes itself from siblings by declaring it is 'the ONLY tool that writes to a design document', which separates it from set_style, edit_text, add_section and create_page.

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 concrete usage strategy: send a whole page in one call rather than one node at a time, and pass baseVersion from get_site_context or get_page_context. It names the sibling tools that supply the version. It stops short of explicit when-not-to-use guidance relative to the single-purpose siblings (set_style, edit_text), leaving that boundary implied.

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