apex_begin_batch

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

Annotations already indicate the operation is idempotent and non-destructive. The description adds the behavioral detail that operations are queued for a single round-trip, implying the tool does not execute them immediately. This is useful context but not extensive; no contradictions with annotations.

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?

Single sentence, front-loaded with the verb, and conveys both action and purpose without wasted words. Excellent.

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 zero-parameter tool with output schema and annotations providing safety details, the description sufficiently conveys the core behavior and purpose. It could mention pairing with apex_commit_batch, but that is inferable from siblings.

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 tool has zero parameters, so the schema is trivially 100% covered. Description adds no parameter-specific meaning, but with no params, the baseline of 4 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?

The description clearly states the verb 'Start' and the resource 'batch mode', and explains the purpose: queue PL/SQL operations for a single DB round-trip. This distinguishes it from sibling tools like apex_run_sql or apex_commit_batch by focusing on the initiation of batching.

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 provides clear context: it's for starting batch mode to queue operations, implying it should be used when multiple operations need to be sent in a single round-trip. It does not explicitly exclude use cases or name alternatives, so it falls short of a 5 but earns a 4.

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