Apply raw edit operations

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

Annotations declare this is a mutation (readOnlyHint=false) but add nothing about atomicity, coordinate units, or op vocabulary — the description supplies all three, notably the all-or-nothing guarantee and 'coordinates here are world units'. It stops short of describing failure behavior (what happens on an invalid op or unknown id) or any confirmation/return signal.

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?

Front-loaded with the core behavior and atomicity before the op catalogue, and the worked example anchors the format. The op list is long but each entry earns its place given the empty item schema; a bulleted layout would scan better than the run-on enumeration.

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 mutation tool with an untyped ops payload and no output schema, the description gives an agent enough to construct valid calls: atomicity, op names, field names, an example, and the coordinate convention. Missing error semantics and per-op required fields keep it just shy of 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?

With schema coverage at 50% and 'ops' typed only as an untyped array of objects, the description carries nearly the entire burden and does so: it enumerates 13 op types with their field shapes and gives a concrete example object. Gaps remain — required vs optional fields per op, the shape of {element} for add_element, and whether ids must already exist.

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 ('Applies a batch of low-level GlideDeck operations atomically') and the op enumeration makes clear this is the raw/escape-hatch editor. It differentiates itself implicitly from higher-level siblings like update_elements and add_text by the word 'low-level', but never names an alternative, so the distinction requires inference.

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 explicit statement of when to reach for this tool versus update_elements, add_text, arrange_slides, or set_theme, all of which overlap with individual ops here. Usage is only implied by 'low-level' and 'batch', which a careful agent can infer but not confidently route on.

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