codex_job_consume_result

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

Description states that the tool deletes the stored record, but annotations set destructiveHint to false. This is a direct contradiction, making the behavioral information unreliable despite the description being otherwise clear.

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?

Four sentences, efficiently structured: core action first, then envelope reference, usage guidance, deletion condition, and detail clarification. No redundant information.

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?

With output schema present, return values are covered. Description explains deletion behavior and when it applies. Could mention error handling (e.g., job not found), but overall sufficient for a tool with high schema coverage and output schema.

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 covers all 3 parameters with descriptions. The description adds context by referencing the envelope from codex_job_result and noting detail behavior, but does not significantly enhance parameter understanding beyond the schema. 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?

Clearly states that it fetches result and deletes stored record. Distinguishes from sibling codex_job_result by specifying the deletion action and usage after polling is no longer needed.

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?

Explicitly says 'Use only when you no longer need to poll or re-read the job' and clarifies that non-done jobs are not deleted. Also references codex_job_result for envelope structure, guiding agent on when to use this vs. the non-consuming version.

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