free_search_advanced

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

Despite no annotations, the description discloses behavioral traits such as quality control via min_confidence filtering, and the 'high-confidence only' hint. It does not cover all possible behaviors (e.g., rate limits, cost), but provides sufficient context for safe invocation.

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 extremely concise with zero waste: one sentence for purpose, a clear list of best-for/not-recommended, and no extraneous text. Front-loaded with the core purpose.

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 7 parameters and no output schema, the description provides enough context for an agent to understand the tool's role and parameters. Lacks details about result format but is acceptable for a search tool.

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%, and the description adds value by contextualizing parameters (e.g., 'high-confidence only' maps to min_confidence, domain filtering to include/exclude_domains). It does not duplicate schema but reinforces usage.

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 performs an advanced search with filters and quality control, and explicitly distinguishes it from the sibling tool 'free_search' by specifying best-use cases and when not to use it.

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 provides explicit guidance on when to use this tool (date ranges, domain filtering, high-confidence only, Chinese content) and when not to (simple queries, recommending 'free_search' instead), with clear alternatives.

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