export_wos

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

No annotations are provided, so the description must cover behavioral aspects. It mentions the return type (download result with file path or error), but does not disclose side effects, authorization needs, or whether it modifies state. The tool implies a read operation (export), but the lack of explicit statement about safety or preconditions (like login_wos) leaves some 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 very concise, front-loads the purpose, and uses a clear list structure for args and returns. Every sentence provides necessary information without waste.

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 two parameters with defaults and an output schema, the description adequately explains the inputs and return. It could add more context about the output format or dependency on a search session, but for a simple export tool it is sufficiently complete.

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 0%, so the description must explain parameters. It clearly describes 'format' with options (bibtex/ris/csv/excel/plaintext) and 'count' with range (1-1000) and default (50), adding 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 the tool exports citation data from the current WoS search results and requires running search_wos first. It uses a specific verb ('export') and resource ('citation data from WoS search'), distinguishing it from sibling tools like search_wos (searching) and get_wos_detail (getting details).

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 explicitly states the prerequisite of running search_wos first, providing clear context for usage. However, it does not explicitly mention whether login is required or when not to use this tool, but for a straightforward export the guidance is adequate.

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