batch_execute

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

Annotations already flag destructive/non-idempotent/open-world, and the description adds substantial value beyond them: default dry-run safety, non-atomicity, returns completed steps on failure, no automatic replay, and name prevalidation. This is exactly the behavioral context an agent needs before a destructive batch.

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?

Four compact sentences, front-loaded with the core operation and safety default; every sentence carries distinct information with no waste.

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 destructive, non-atomic batch tool with no output schema, the description covers safety default, failure semantics, and prevalidation well. It falls short of full completeness by omitting stop_on_error behavior and the table_id targeting already noted in the schema.

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 only 25%, so the description must compensate. It explains dry_run (defaults true, set false to apply) and commands (up to 100, prevalidated names), but says nothing about stop_on_error or table_id, leaving two parameters undocumented in the description.

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?

States a specific verb (Run) and resource (up to 100 native commands) plus scope (sequentially, no interleaving). This clearly distinguishes it from the single-command sibling table_command by emphasizing batch size and ordering.

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?

Gives concrete guidance: prevalidates names, dry_run defaults true and must be set false to apply, non-atomic with no automatic replay. Clear context for safe use, though it never explicitly names alternatives or states exclusions for when not to batch.

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