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

Goes well beyond the annotations by disclosing atomicity ('Nothing is changed when one item is wrong'), optimistic-concurrency behavior ('or its slide changed meanwhile'), and the version-history effect. These are non-obvious traits not derivable from readOnlyHint/destructiveHint, and they do not conflict with destructiveHint=false since deletes are recoverable through the created version.

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 one-step value proposition and otherwise dense with essential semantics; there is some packing of three operations into a single sentence, but no filler sentences.

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?

A high-complexity batch mutation tool whose gotchas (atomicity, concurrency check, history version, response verbosity) are all covered; return values are further backed by an output schema, so nothing critical is missing.

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?

The schema types `edits.items` only as a generic object, and the description compensates fully by spelling out the item keys (slide_id, add, update, delete, at_bottom, base_version) and the semantics of add placement, update targeting (id/ids/inside), and delete. Without it, the array would be opaque.

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?

Specific verb+resource+scope: 'Change blocks on many slides in one step (and one version in the history)'. The batch scope implicitly distinguishes it from edit_blocks/update_slide, but no sibling is named explicitly, so an agent must infer that edit_blocks is the single-slide variant.

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?

The 'in one step' phrasing implies this is the batch alternative to single-slide editing and surfaces the versioning advantage, but there is no explicit when-to-use/when-not statement or named alternative among the many sibling write tools (edit_blocks, update_slide, add_slide, reorder_slides).

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