apex_commit_batch

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

The description discloses the rollback_on_error default, which adds behavioral context beyond the annotations (which are all false). However, it does not mention other important traits such as whether the operation is irreversible or clears the queue.

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 concise sentence with a parenthetical, front-loading the primary action.

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 tool with no parameters and an output schema, the description is minimal. It provides some rollback context but does not address the tool's side effects or post-conditions, leaving gaps for a mutating operation.

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?

The input schema declares zero properties, but the description references a `rollback_on_error` parameter that is not in the schema, creating confusion. This is misleading rather than additive.

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 states a specific verb ('Execute') and resource ('all queued batch operations'), clearly distinguishing this from siblings like apex_begin_batch and apex_dry_run_preview.

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 this is the final step for queued operations but does not explicitly state when to use it versus alternatives, nor mention prerequisites like beginning a batch or previewing with apex_dry_run_preview.

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