Batch Search CNBS Data

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds that results are grouped by keyword but does not disclose additional behavioral traits like rate limits or error handling. With annotations covering safety, the description offers moderate added context.

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 concise with a front-loaded purpose, structured Args/Returns sections, and a practical example. Every sentence adds value, and the length is appropriate for a tool with two parameters.

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 simplicity (2 parameters, no output schema), the description fully covers purpose, parameter semantics, return structure, and usage example. No gaps are apparent for effective invocation.

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 descriptions for both parameters. The description adds value by providing an example ('keywords=["GDP", "CPI", "出生率"]') and explaining the return format ('按关键词分组的搜索结果'), which goes beyond the schema's basic descriptions.

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 explicitly states it performs batch search for multiple keywords simultaneously, improving efficiency. The title 'Batch Search CNBS Data' and the description '批量搜索多个关键词的统计数据' clearly specify the verb (batch search) and resource (CNBS data). It distinguishes from sibling tools like 'cnbs_search' which likely handles single keywords.

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 indicates usage when multiple keywords need to be queried at once ('一次性查询多个指标，提高效率'), but does not explicitly mention when not to use or name alternatives. However, the context implies it replaces multiple single searches.

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