codex_task

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

With no annotations, the description must disclose behavioral traits. It mentions returning a final response but does not detail side effects like file modifications, sandbox mode implications, network access, or potential long execution times. The term 'autonomous' hints at self-direction but leaves many behavioral aspects unclear.

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 sentence, which is concise but lacks necessary detail. For a tool with six parameters and no annotations, the description should include more information to be useful. It is under-specified rather than efficiently comprehensive.

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?

Given the tool's complexity (6 parameters, no output schema, no annotations), the description is severely incomplete. It fails to explain parameter semantics, sandbox modes, or thread lifecycle. The single sentence does not provide enough context for correct tool invocation.

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 only 17% (only 'prompt' has a description). The tool description adds no additional meaning to parameters; it does not explain workingDirectory, model, sandboxMode, networkAccessEnabled, or webSearchEnabled. The description does not compensate for the low schema coverage.

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 it runs an autonomous coding task in a new Codex thread and returns the final response. The verb 'run' and the resource 'autonomous coding task in a new Codex thread' are specific, and the tool is differentiated from siblings like codex_run or codex_continue by explicitly mentioning 'new Codex thread'.

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 does not explicitly state when to use this tool versus alternatives. However, the phrase 'in a new Codex thread' implies it is for starting a fresh task, which provides some implicit guidance. No exclusions or when-not-to-use cases are mentioned.

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