douyin_logout

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

Annotations carry only a title with no destructiveHint or readOnlyHint, so the description must shoulder the safety burden; it does disclose the blast radius ("所有" cookies in the browser profile), which is the key behavioral fact. It does not say whether server-side session is also invalidated or that re-login via douyin_login_qrcode is required afterward.

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?

One sentence with the action front-loaded and the use case in a trailing parenthetical; no word is wasted. Nothing is buried or repeated.

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 parameterless, output-schema-less cleanup tool this is nearly complete: what is cleared and when to call it. The missing piece is post-condition behavior (that the account becomes logged out and a fresh QR login is needed), which matters given no destructive annotation.

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 tool takes zero parameters, so there is no parameter meaning to add and the baseline for a no-param tool applies. The description adds no argument-level detail because none exists.

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?

States a specific verb and resource with scope: "清掉浏览器 profile 里的所有抖音 cookie" tells the agent exactly what is removed and where. It is clearly the sole logout/cleanup tool among siblings (login_qrcode, login_status), though it never names those siblings to contrast with.

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 parenthetical "换号或登录态异常时用" gives two concrete triggering conditions, which is real when-to-use guidance. It stops short of exclusions or explicitly pointing to douyin_login_status as the diagnostic alternative before nuking cookies.

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