codex_get_chat_status

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

With empty annotations, the description must disclose behavioral traits. It only states what is excluded (DeepSeek, full transcript) but not what is included, nor any details about authorization, rate limits, or side effects for this query tool.

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, clear sentence with no redundancy. It could be enhanced by structuring parameter details, but it is appropriately concise for a simple retrieval tool.

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 presence of an output schema, the description does not need to detail return values. However, it lacks explanation of the optional project_id parameter and does not clarify when to use this tool versus the full chat retrieval, leaving moderate gaps.

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 0% with no descriptions for parameters. The description mentions 'short previews' hinting at preview_max_chars but does not explain the meaning or purpose of chat_id, project_id, or preview_max_chars, leaving the agent to infer from the schema alone.

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 verb 'Get', the resource 'Codex chat status and short previews', and the constraints 'without DeepSeek and without full transcript content', effectively distinguishing it from sibling tools like codex_get_chat.

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 context by noting what is excluded (DeepSeek, full transcript), implying lightweight use, but does not explicitly state when to use this tool versus alternatives like codex_get_chat or codex_get_turn_status.

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