smart_search

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

No annotations are provided, so the description carries full burden. It does not disclose whether the tool is read-only, whether it modifies data, or any special behaviors like rate limits or authentication. The examples hint at querying, but explicit behavioral disclosure is missing.

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 well-structured with sections for introduction, examples, args, returns, and additional examples. It is not overly verbose, though some redundancy exists (e.g., examples in both intro and dedicated section). The bilingual content is acceptable but could be streamlined.

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 output schema exists (though not shown), the description doesn't need to detail return values. However, it only vaguely states '智能搜索结果'. It lacks details on error handling, pagination, or ambiguous query behavior. For a moderately complex tool, more context would be beneficial.

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?

With 0% schema description coverage, the description compensates well by explaining each parameter: 'description' as natural language, 'context' with allowed values (genomics/proteomics/pathway), 'filters' as filter conditions with an example, and 'max_results' as maximum result count. This adds significant meaning beyond the schema.

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 it performs intelligent semantic search by understanding natural language descriptions and executing queries. The examples illustrate the purpose well, but it does not explicitly differentiate from sibling tools like 'advanced_query' or 'get_data'.

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 use for natural language queries through examples, but it lacks explicit guidance on when to use this tool versus alternatives (e.g., 'advanced_query' for structured queries). No when-not-to-use or exclusion criteria are provided.

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