codex_native_prune

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

No annotations are present, so the description carries full burden. It discloses what gets deleted (finished jobs, logs, images) and that running jobs are safe, but omits details like irreversibility, authorization needs, or rate limits. The dryRun mention helps, but overall transparency is moderate.

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?

Two concise sentences with no filler. The first sentence states the core purpose, and the second provides a critical usage tip. Every word earns its place.

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 three parameters, no output schema, and no annotations, the description is fairly complete: it explains what is deleted, the retention condition, and that running jobs are preserved. It could elaborate on the interplay of keepJobs and maxAgeDays, but the schema covers that detail.

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 100% and the description adds little beyond what the schema already explains for each parameter (dryRun, keepJobs, maxAgeDays). The description provides context but no additional parameter semantics, so baseline 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 deletes finished job records, logs, and generated images beyond a retention window, explicitly noting that running jobs are never removed. This distinguishes it from sibling tools like start, cancel, or list operations.

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 advises using dryRun first to see what would be deleted, providing explicit usage guidance. It does not compare directly to sibling tools, but the action of pruning is distinct enough that no further differentiation is needed.

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