batch-codex

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

With no annotations provided, the description must cover behavioral traits. It mentions 'batch' and 'sequential' execution, implying multiple tasks. However, it does not disclose potential side effects, authentication needs, rate limits, or what happens on failure. The 'automated transformations' hint at code changes, but this 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 concise: two sentences front-load the purpose and usage, with no wasted words. Every sentence adds value.

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?

Despite high schema coverage, the tool has 12 parameters and no output schema. The description does not explain return behavior, error handling, or how parallel/stopOnError work. This leaves gaps for an agent selecting the tool.

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 100%, so the description does not need to detail each parameter. The description mentions 'several tasks' and 'mass refactoring,' which aligns with the 'tasks' parameter but adds little beyond the schema. Baseline of 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?

The description clearly states the tool's purpose: 'Run multiple tasks through OpenAI Codex in batch.' It specifies the verb ('run'), the resource ('OpenAI Codex'), and the batch nature, distinguishing it from single-task siblings like 'ask-codex'.

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 usage context: 'Use when the user wants Codex to handle several tasks sequentially.' It gives examples like mass refactoring and bulk code changes. However, it does not explicitly mention when not to use this tool or name alternative tools for single tasks.

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