document_apply_operations

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

Annotations only declare destructiveHint=true, so the description carries extra burden and delivers: it discloses that operations are validated sequentially against the preceding in-memory result and that a failure leaves the source untouched (all-or-nothing atomicity). That is meaningful behavioral context beyond the annotation and is consistent with destructiveHint. It omits authentication/workspace requirements and dryRun semantics.

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 tight sentences with zero waste. The purpose is front-loaded in the first clause, and the second sentence adds the atomicity guarantee, so every sentence earns its place.

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 highly complex, many-branch transactional tool with an output schema in place, the description covers atomicity but omits concurrency-control semantics (expectedRevision), the dryRun flag's effect, and any usage routing against sibling mutation tools. Adequate but with clear gaps given the tool's complexity.

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 0% and the description references none of the six parameters. It says nothing about expectedRevision (optimistic concurrency), dryRun, path, or workspaceId, so it fails to compensate for the prose-description gap. The schema's rich enums/consts describe operation shape structurally, but the top-level control parameters remain unexplained.

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 target: 'Applies a bounded ordered design transaction to an SVG.' The phrase 'design transaction' conveys that this is a batch/atomic operation rather than a single-element mutation, which distinguishes it conceptually from siblings like elements_create or elements_update. However, it never names those siblings or explicitly contrasts the batch approach with the single-operation tools.

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?

There is no when-to-use guidance, no exclusions, and no mention of alternatives. An agent cannot tell from the description why it should batch operations here versus calling elements_create/elements_update/elements_transform individually. The only contextual hint is implicit in the word 'transaction'.

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