execute_batch

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

With no annotations, the description must fully disclose behavior. It mentions transactionality but omits critical details: return value, error handling on partial failure, the role of the 'confirmed' parameter for destructive operations, and default behavior for connections and database.

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, well-targeted sentence conveys the core purpose efficiently. Could be slightly more structured (e.g., bullet points) but remains clear without unnecessary text.

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 4-parameter tool with no output schema, the description is too sparse. It lacks explanation of return values, error scenarios, and how parameters like 'confirmed' affect behavior, leaving the agent with significant gaps.

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 75%, so the schema already explains most parameters. The description adds no extra param meaning beyond what's in the schema, so baseline 3 is appropriate.

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?

Description clearly states the tool executes multiple DML statements within a single transaction, which is specific and informative. It distinguishes from siblings like 'execute' (single statement) or 'execute_ddl' (DDL) through the focus on DML and batching, though not explicitly.

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 a single transaction' implies usage when atomicity is required, but there is no explicit guidance on when to use this tool versus alternatives like 'execute' for single statements or when not to use it (e.g., for read-only operations).

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