search

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds meaningful behavior context beyond the annotation: aggregation across multiple search engines, deduplication, optional full-content fetching, and image-search behavior returning direct image URLs.

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 tightly written in three sentences: purpose, usage cue, and additional capability. Every sentence contributes distinct information with no filler or repetition of schema details.

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?

For a tool without an output schema, the description covers the core behavior, sources, dedup, content fetching, and image search. It does not describe the exact result shape or valid categories values, but the schema covers parameters and the high-level behavior is sufficient for most invocation decisions.

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%, so every parameter already has a description. The tool description adds high-level meaning by mentioning content fetching and image search, but it does not map these to specific parameter values like categories; the schema remains the primary source for parameter semantics.

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 a specific verb and resource: 'Search the web across Baidu/Bing/Sogou/WeChat/Google', adding aggregation and dedup, optional content fetching, and image search with direct image URLs. This strongly distinguishes it from sibling tools like fetch or session navigation, even though no sibling is named explicitly.

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 explicitly says 'Use when the agent needs to FIND information online' and notes it 'replaces a search API'. This gives clear when-to-use guidance, though it does not explicitly address when to prefer sibling tools like fetch for fetching a specific known URL.

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