Batch Execute

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

With no annotations to carry the safety/behavior burden, the description discloses three key behavioral traits: operations apply in order, failures are recorded per-op while the batch continues by default, and the entire batch is wrapped in a single undo group. These details are critical for an agent to predict the tool's side effects accurately.

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 sentences, each dense with information: purpose, execution semantics, and a concrete workflow example. There is zero fluff; every word contributes to understanding or differentiation.

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 composite operation with no output schema, the description fully equips an agent to decide when to use it and what to expect regarding ordering, error handling, and undo behavior. It also addresses the main caveat (nested batch restriction) within the schema, and the workflow suggestion ties into the broader tool ecosystem.

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 value beyond the schema by explaining the op types (through examples of handler names) and hinting at the workflow for populating them. It doesn't detail individual argument structures, but combined with the schema, the agent has sufficient clarity.

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 begins with a specific verb and resource ('Run many generic ops in one RPC'), immediately distinguishing it from singular sibling tools like set_params or create_entity. It also clarifies scope by explaining the sequential application, error handling, and undo grouping, making it unmistakable what this tool does.

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 provides a clear use case ('apply X to all matching entities') and explicitly recommends pairing with list_entities and name_pattern to obtain handles. However, it does not explicitly state when NOT to use this tool or name an alternative, missing the full 'when-not/alternatives' criterion.

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