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 burden. It states 'execute multiple commands in sequence' and 'single round-trip' but does not disclose important behavioral traits such as partial execution on failure, order guarantees, or side effects. The existence of 'stopOnError' is not mentioned in the description.

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?

Two concise sentences, front-loaded with the main action. No wasted words, and the key benefit (single round-trip) is mentioned early. Despite its brevity, it covers the core purpose effectively.

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?

Given the tool's batch execution nature and lack of output schema, the description is insufficient. It does not explain what 'commands' refer to (e.g., names of other tools), how errors are handled, or what the return value is. The agent lacks enough context to use it correctly without additional inference.

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 no additional meaning beyond what the schema already provides for the parameters. It does not explain the relationship between commands or what valid command values are.

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 it executes multiple commands in sequence with a single round-trip, which is a specific verb+resource. It also mentions it's ideal for complex operations with multiple steps. However, it doesn't explicitly differentiate from sibling tools like 'clone_multiple_nodes' or 'delete_multiple_nodes', which also handle multiple steps but are more specific.

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 only says 'Ideal for complex operations that require multiple steps,' implying when to use, but provides no guidance on when not to use or what alternatives exist. It does not mention trade-offs like error handling or atomicity, which are crucial for batch operations.

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