toutiao_login

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

With no annotations, the description carries the full burden of disclosure. It explains the main steps: opening a browser, obtaining a QR code, waiting for scanning, and automatically saving cookies to cookies.json. This is a meaningful side effect disclosure, though it omits potential timeout behavior or error handling.

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, front-loaded sentence that efficiently communicates the action, purpose, and side effect without extraneous content.

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 description provides a comprehensive overview of the login process and its side effect, which is sufficient given the lack of an output schema. It could explicitly mention that login is a prerequisite for sibling tools, but this is a minor omission.

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 schema has zero parameters, so the baseline is 4. The description does not need to add parameter details because none exist, and it does not attempt to explain any.

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 specific verb '登录' (login) and the resource '今日头条' (Toutiao), and outlines the login flow: open browser, get QR code, wait for scan, and save cookie. This distinctly separates it from sibling tools like check_status, logout, and publish_article.

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 implies the tool is for authenticating before using Toutiao-related operations, but it does not explicitly state when to use it versus alternatives. No exclusions or conditional guidance are provided, leaving usage context lightly implied.

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