cnki_download

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

No annotations are provided, so the description carries the full burden. It transparently describes the side effect of saving a file to the downloads/ directory and mentions the need for institutional login. It does not detail error handling or potential overwrites, but the core behavior is disclosed.

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, consisting of two short sentences within the tool description. It efficiently covers the input, action, output location, and a critical prerequisite without unnecessary wording. The structure is clean and direct.

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 simple download tool, the description is complete: it states what it does (download PDF), how (auto-click button), where it saves (downloads/), and a key condition (institutional login). No additional information is necessary for an agent to decide when to call it.

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 single parameter 'url' has a clear description in the schema: '知网文章详情页URL' (CNKI article detail page URL). The tool description repeats this, reinforcing the expected value. Schema coverage is 100%, and the description adds no ambiguity, though it also offers no extra details 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's purpose: downloading CNKI paper PDFs. It specifies the input (article detail page URL) and the action (auto-click download and save to downloads/). This distinguishes it from sibling tools like search or get_article, which have different functions.

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 implicitly indicates usage by specifying the required input and the prerequisite of institutional login. It does not explicitly mention alternatives, but the distinct purpose makes it clear when to use this tool over others. The login requirement provides important context for when it can be used.

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