执行WOS SCI检索

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

The description discloses the stop condition at 500 hits and the filtering behavior (by year, unit, SCI-EXPANDED), which adds context beyond annotations. It also mentions exporting complete records, aligning with readOnlyHint=false. However, it does not specify the export destination or whether run status is updated, leaving some behavioral gaps.

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 dense sentence that efficiently packs the tool's purpose, execution details, filtering, and stop condition without fluff. Every clause contributes essential information, and it is well front-loaded.

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?

The tool is moderately complex, and while the output schema exists, the description misses parameter semantics and does not clarify prerequisites (e.g., creating a run first) or edge cases. It covers the main behavior but leaves gaps for an agent to decide when and how to invoke the tool correctly.

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 input schema has a single required parameter run_id with no description, and the description does not explain what run_id refers to or how it relates to the search run. Schema coverage is 0%, and the description fails to compensate, providing only implicit meaning through the word '运行中的'.

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 executes an advanced search in WOS Core Collection using a dedicated Chrome, exports complete records, and filters them by year, unit, and SCI-EXPANDED. The phrase '运行中的' (ongoing) distinguishes it from creating a search run, making it distinct from sibling tools like create_search_run. It includes specific action, resource, and constraints.

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 context such as the need for a dedicated Chrome and the stop condition at 500 hits, but it does not explicitly state when to use this tool versus alternatives like create_search_run or get_run_status. It implies usage for an existing run via '运行中的', but no exclusions or alternative recommendations are given.

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