search_web

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only mentions the execution channel (Google/Bing via Cloud API) but does not indicate whether the operation is read-only, what the response format looks like, rate limits, or any side effects. This is insufficient for a network-backed search 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 sentence that conveys the core function without wasted words. It is front-loaded and appropriately sized for a simple one-parameter tool, with no redundant information.

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 there is no output schema and no annotations, the description should clarify what the agent will receive (e.g., list of results, titles, URLs) and perhaps contrast with sibling tools like fetch_url. It provides only the minimal identity of the tool, leaving the agent without enough context to choose it confidently or understand its output.

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%: the lone parameter 'query' is described in the schema as 'Từ khóa cần tìm kiếm trên internet' (keyword to search on the internet). The tool description adds no additional meaning beyond the schema's existing definition, 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 clearly states the tool's function: searching online information via Google/Bing through TXAHUB's Cloud API. It specifies the verb 'search' and the resource (web), but it doesn't differentiate it from closely related sibling tools like fetch_url or search_code beyond the general 'online' scope.

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?

No usage guidance is provided. The description does not explain when to use this tool versus alternatives such as fetch_url, file_search, or search_code, nor does it mention any constraints or prerequisites.

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