batch_execute

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

With no annotations, the description carries the full burden of disclosing behavior. It clearly states that failures are reported per item, that this is transport-level batching, and that atomic rollback is not provided. This meaningfully exceeds a bare 'batch requests' 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?

The description is compact, front-loaded with the primary purpose, and uses a clarifying contrast rather than verbose prose. Every sentence adds meaningful information.

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 covers purpose, batching semantics, failure behavior, and parameter meaning. It doesn't describe response shape or per-item result ordering, but those may be established elsewhere; for an invocation decision, the context is solid.

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?

Despite 0% schema coverage, the description documents both parameters inline: ops as a list of {method, params} objects, and abort_on_error with its default false behavior. This is enough for an agent to construct a basic call, though item-level details remain open.

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 clearly states the action ('Run a list of router requests') and the key distinction ('ONE bridge round trip'), and it clarifies that this is batching rather than a transactional rollback. It doesn't explicitly name a sibling alternative like bridge_router_call, but the intent is unmistakable.

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 conveys when to use it: when multiple router requests need to be executed in a single round trip. It also gives an exclusion ('not a rollback transaction'), which helps prevent misuse, though it does not explicitly mention alternative single-call tools.

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