codex_get_queue_status

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

With no annotations, the description carries full burden. It declares a read operation ('Read') and gives behavioral advice (do not retry). While it doesn't cover auth or rate limits, it sufficiently describes the read nature and outputs for this context.

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 sentences, front-loaded with the core purpose, no fluff. 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?

Output schema exists, so return values are covered. However, the description lacks guidance on input parameters (status filter, limit) which is needed for proper use. It is borderline adequate but missing key parameter context.

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 0%, so description should explain parameters. However, the description mentions 'queued reasons, running operations, worker assignment' but does not describe the 'status' filter or 'limit' pagination parameter. These are significant omissions.

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 reads 'durable queue state, queued reasons, running operations, and worker assignment', specifying a verb and resource. This distinguishes it from sibling tools like codex_get_worker_status and codex_get_operation_status.

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 explicit usage context: 'Use this to understand slot pressure or lock waits' and a clear directive: 'Do not retry when queued work already exists'. This helps the agent decide when to invoke the tool and what not to do.

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