search_simple

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the tool performs '简单关键词搜索' but doesn't describe what kind of results are returned, whether there's pagination beyond the 'size' parameter, error conditions, or performance characteristics. The example usage shows basic syntax but lacks behavioral 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 efficiently structured with a clear title, parameter list, and examples. Every sentence serves a purpose - the title establishes function, parameters explain inputs, and examples demonstrate usage. The bilingual nature (Chinese description with English parameter names) is slightly inconsistent but functional.

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 search tool with 4 parameters, no annotations, and no output schema, the description is incomplete. It explains parameters well but lacks crucial information about return format, error handling, performance limits, or how results are structured. The examples help but don't compensate for missing behavioral context.

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?

The description provides clear parameter documentation in Chinese, explaining each parameter's purpose: 'index: 索引名称' (index name), 'keyword: 搜索关键词' (search keyword), 'field: 搜索字段（可选，不传则全字段搜索）' (search field, optional, searches all fields if not provided), and 'size: 返回数量' (return count). With 0% schema description coverage, this documentation is essential and well-explained.

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 '简单关键词搜索' (simple keyword search), which is a specific verb+resource combination. It distinguishes itself from the more general 'search' sibling tool by emphasizing simplicity, though it doesn't explicitly contrast with other search-related siblings like 'search_template' or 'knn_search'.

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 no guidance on when to use this tool versus alternatives. With many sibling tools including 'search', 'search_template', 'knn_search', and 'msearch', there's no indication of when this simplified version is appropriate versus more complex search operations.

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