Run RPC pipeline

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

The description adds behavioral context beyond annotations by specifying the 50-operation limit, round-trip optimization, sequential/concurrent modes, and stop-on-error option. However, it does not disclose error handling details, whether operations are atomic, or what the return format is. Annotations already declare destructiveHint, so the description's additional context is moderate value.

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 a single, focused sentence that front-loads the core function and includes all key options without unnecessary words. Every phrase earns its place, making it highly efficient.

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?

This is a complex tool with 5 parameters, a nested operations array, no output schema, and low schema coverage. The description is too brief to cover critical aspects like how to specify operations (method names), what 'supported' means, error/result behavior, or the impact of clientId and timeoutMs. It leaves the agent with significant unknowns for successful invocation.

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 only 20%, so the description must compensate. It clarifies 'sequentially or concurrently' (mode), 'stop-on-error' (stopOnError), and 'up to 50' (maxItems for operations). Yet it does not explain operations object structure (method/params), clientId, or timeoutMs, leaving significant gaps for the required operations parameter.

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 tool's function: running up to 50 client operations in a single round trip, with options for sequential/concurrent execution and stop-on-error. It distinguishes itself from sibling tools (individual operations) by explicitly being a batch wrapper, making its purpose 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 phrase 'in one round trip' clearly implies usage when multiple operations need to be performed together to reduce overhead, and 'sequentially or concurrently' indicates execution modes. However, it does not explicitly mention when NOT to use this tool or name specific alternative tools for single operations, so it lacks explicit exclusions.

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