obs-execute-batch

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

No annotations are provided, so the description carries the full behavioral burden, and it does not disclose what happens when one request in the batch fails, whether partial effects persist, what the response contains, or that destructive members are gated behind confirm and OBS_PROTECT_DESTRUCTIVE. Worse, 'atomically' implies all-or-nothing semantics that the schema undercuts via 'haltOnFailure' defaulting to false, so the one behavioral claim it does make is likely to mislead.

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?

A single front-loaded sentence with no filler, and the verb lands first. The trailing '(OpCode 8 RequestBatch)' parenthetical is marginally useful protocol anchoring rather than wasted words, but the whole definition is thin enough that conciseness comes at the cost of completeness.

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 batch executor that can carry destructive operations, a 100%-covered schema plus one sentence is only just adequate: the schema covers inputs, but failure semantics, atomicity reality, and the confirm-protection interaction are absent. No output schema exists, so the description would ideally say something about how per-request results come back.

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%, with the enum on executionType and defaults for haltOnFailure and executionType already documented in the schema, so the baseline is 3. The description adds no meaning beyond that—nothing on how requests are formed, what requestType values are valid, or what confirm actually gates.

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?

The description names a specific verb and resource: 'Executes multiple OBS WebSocket requests atomically as a batch,' and anchors it to the protocol construct '(OpCode 8 RequestBatch)'. This clearly separates it from the ~150 single-request siblings such as obs-set-current-scene or obs-trigger-hotkey-by-name. It stops short of the 5-tier bar because it does not state scope or contrast explicitly with calling those single-request tools repeatedly.

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?

'Atomically as a batch' hints at the batching rationale, but there is no explicit when-to-use or when-not-to-use guidance, no mention that this is the preferred path when applying several state changes together, and no note about ordering or pacing. With this many single-request siblings an agent gets no help deciding between one batch call and N individual calls.

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