Batch Execute

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

With no annotations provided, the description fully carries the burden and does so well: it discloses main-thread execution, sequential application, per-op error recording, default undo grouping, active-document binding/restoration, and rejected operation categories. This goes far beyond a minimal 'run multiple ops' statement.

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?

Three dense sentences with no filler; the core action is front-loaded and operational details follow logically. Every sentence earns its place by conveying a distinct behavioral aspect of the tool.

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?

The description combined with the fully documented schema covers execution semantics, error handling, undo behavior, and scoped document handling. The main omission is the shape of the return value, which matters more because there is no output schema.

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 100%, so the baseline is 3. The description adds meaningful semantics by explaining the default behavior of undo_group and stop_on_error and the full document_name scoping model. It does not discuss timeout_ms, but the schema already documents that parameter clearly.

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 action ('Run many generic ops in one main-thread RPC') and clearly identifies the resource as a composite operation executor. The batching behavior is distinct from the many individual sibling tools, so an agent can tell this is a container for other registered handlers.

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 description explains ordering, per-op failure continuation, undo grouping, and document_name scoping, giving clear context for when this tool is appropriate. It does not explicitly name alternative tools or say 'use this instead of running individual ops', but the use case is strongly implied.

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