高级搜索

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

No annotations are present, so the description must carry the behavioral burden. It only mentions features (Boolean, fuzzy, exact) but does not disclose side effects, performance implications, or other behavioral traits such as rate limits or data handling.

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, clear sentence that efficiently conveys the tool's key features. No unnecessary words or fluff.

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 (7 parameters, advanced features, output schema), the description is adequate but not comprehensive. It lacks details on query syntax, feature interactions, and return value structure, though the output schema may compensate for the latter.

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% with individual parameter descriptions. The description adds minimal value by summarizing features (Boolean, fuzzy, exact) already implied by parameter names and descriptions. It does not explain parameter interactions or syntax 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 is an 'advanced search' with Boolean operators, fuzzy matching, and exact matching, which distinguishes it from simpler search tools like 'search_papers'. However, it does not explicitly name the resource being searched (e.g., papers), though context implies 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?

No guidance is provided on when to use this tool versus alternatives. The description merely lists features without explaining when Boolean operators are beneficial or when to prefer 'search_papers'.

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