advanced_web_search

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

No annotations are provided, so the description must disclose behavioral traits. It mentions optional Sonar and result shaping but does not explain potential side effects, response formats, rate limits, or any safety implications. It lacks details on how the tool modifies results or what happens with Sonar models.

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, front-loaded sentence that is easy to parse and contains no fluff. However, it is so brief that it sacrifices detail; still, it earns a high score for conciseness.

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 tool's complexity (16 parameters, enums, optional Sonar), the description is too minimal. It does not explain return values (no output schema), how result shaping works, nor when to choose different engines like sonar_answer vs raw_search. This leaves significant gaps for an agent to use the tool correctly.

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 100%, so the schema fully documents each of the 16 parameters. The description only generically mentions complex parameters without adding meaning to any specific parameter, so it sits at the baseline of 3.

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 states this is an advanced version of web_search, supporting complex retrieval parameters and result shaping, with optional Sonar direct answers. It clearly identifies the tool's function and distinguishes it from the sibling web_search by emphasizing 'advanced' features.

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 implies advanced_web_search should be used when complex retrieval parameters or Sonar are needed, but does not explicitly state when not to use it or compare with alternatives other than referencing web_search. The phrase '需要时才开' gives a hint to only enable Sonar when necessary, but no clear decision framework.

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