Server Quality Checklist

Tool Scores

• codex_web_searchA
  4.4/5.0
  Behavior4/5

  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.

  Conciseness4/5

  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.

  Completeness5/5

  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.

  Parameters3/5

  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.

  Purpose5/5

  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.

  Usage Guidelines5/5

  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.

• codex_web_researchA
  4.6/5.0
  Behavior5/5

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

  With no annotations, the description carries the full burden and does so richly. It discloses that operations can be chained using ref_id across calls, that session context is auto-maintained, that open() inlines [cN: text → domain] markers where N is the clickable id, that responses contain ref_id, and that valid Codex login credentials are required. These go far beyond schema details.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness4/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a dense paragraph, but every sentence earns its place: purpose, workflow, mechanics, and requirements. It is logically organized and front-loaded with the tool's core purpose. Slightly long, but appropriate given the operational complexity it must convey.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness4/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  For a complex multi-step tool with no output schema, the description covers the workflow and return of ref_id, but does not specify the exact structure of search results or opened document bodies. This is a minor gap; the description is still sufficient for an agent to invoke the tool correctly.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters5/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Although schema coverage is 100%, the description adds crucial semantics: it explains the meaning of ref_id as a chaining token, how the click id N is derived from inline markers, and that session_id overrides the auto-maintained session. This makes the parameters actionable beyond their raw names and schema descriptions.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description explicitly identifies the tool as a multi-step deep research tool and details the exact operation sequence: '搜索 → 打开文档 → 页内查找 → 点击链接' (search, open, find, click). It names the underlying engine (Codex web retrieval + document browsing) and clearly distinguishes itself from the sibling codex_web_search by emphasizing multi-step research.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines4/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  It provides a concrete typical workflow (search → open → find → click) and explains that operations can be combined in one call or split across rounds using session context. It mentions suitability for non-Anthropic models, but does not explicitly state when one should choose this tool over codex_web_search or describe exclusions, missing the highest bar.

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