login_cnki

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 discloses key behaviors: opens a visible browser window, requires manual login, automatically persists login state, and returns login status information. It does not discuss failure scenarios or side effects, but for a simple login tool this is adequate.

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 short and front-loaded with the primary action. Every sentence adds value: purpose, usage guidelines, behavioral note, and return value. No wasted words.

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 low complexity (0 parameters, straightforward login task) and the presence of an output schema (mentioned but not detailed), the description covers the essential aspects. It might be improved by mentioning prerequisites (e.g., valid CNKI account), but it is largely 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?

The input schema has zero parameters and schema description coverage is 100%. The description does not add parameter information because none exist. Baseline for 0 parameters is 4, and the description is sufficient.

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 opens a login page for manual login to CNKI (知网). It distinguishes from siblings like login_wos by specifying the platform. It also notes that it is for first-time use and that login state persists automatically.

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 says '首次使用时调用一次，之后登录态会自动持久化', providing clear guidance on when to use the tool (once initially) and implying that subsequent calls are unnecessary. It also notes that it opens a visible browser window, which informs the user of the interactive nature.

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