codex_web_search

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

With no annotations provided, the description carries the full burden. It discloses authentication requirements, output structure (answer text + sources with ref_id), and model independence. However, it does not mention potential failure modes, rate limits, or result quality nuances, leaving some behavioral details undisclosed.

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 composed of three sentences, each carrying distinct value: function, use case/motivation, and prerequisites. It is efficiently structured and front-loaded with the core purpose, though slightly longer than the bare minimum.

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?

Without an output schema, the description adequately explains return values (answer text and sources with ref_id). It also covers authentication, model independence, and relationship to the sibling tool, making it contextually complete for a search tool with four parameters and no annotations.

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 schema already describes all four parameters clearly. The description adds no additional meaning about parameter usage or syntax beyond what the schema provides, so the baseline of 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 explicitly states the tool performs real-time web search via OpenAI Codex's search endpoint, and clearly differentiates it from the sibling tool by mentioning ref_id for use with codex_web_research. The verb '执行实时联网搜索' is specific and unambiguous.

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?

It explicitly describes when to use this tool: when the underlying model is non-Anthropic and native WebSearch fails or underperforms. It names the alternative (native WebSearch) and the complementary sibling (codex_web_research), providing clear context for selection.

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