batch_delete_rows

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It clearly signals a destructive delete operation and the 200-row limit. However, it omits details about handling non-existent row IDs, partial failures, atomicity, or return values—important for a batch mutation. The phrase 'at once' hints at atomicity but is not explicit.

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, front-loaded sentence that conveys the core operation, the batch nature, the limit, and the input format. Every word earns its place with no redundancy or filler.

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 tool is relatively simple with two well-documented parameters, but the lack of an output schema and annotations leaves gaps. The description does not mention what the tool returns, whether deletion is atomic, or how errors are handled. For a batch operation, information about partial failure or success indication would improve completeness.

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 coverage is 100%: both table_id and items have descriptions. The tool description restates the array and max limit but adds no additional semantics beyond the schema. Since the schema already defines each parameter clearly, the description adds marginal value, meeting the baseline of 3.

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 (Delete), resource (multiple rows), and mode (batch, up to 200). This distinguishes it from sibling tools like delete_row, which handles single rows, and batch_create_rows/batch_update_rows. The phrasing 'at once' clarifies the batch scope.

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 implies when to use this tool: when deleting multiple rows in one operation. It provides clear context for batch deletion but does not explicitly exclude single-row deletion via delete_row or mention alternatives. The sibling tool list makes the distinction evident, but no explicit when-not guidance is given.

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