logout

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

Annotations already establish readOnlyHint=false and openWorldHint=false, so the mutating, non-open-world profile is covered. The description adds one genuinely useful behavioral detail beyond annotations — that the deletion targets *locally stored* credentials rather than server-side session state — but says nothing about reversibility or whether re-authentication is required.

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 short, front-loaded clause with no filler; the bilingual synonym in parentheses earns its place by improving retrieval match for 'log out'/'sign out'. Every token serves a purpose.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. However, for a destructive local action the description omits the practical consequence (session invalidation, need to re-login), leaving a meaningful gap for an agent deciding whether 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?

There is a single parameter with 100% schema description coverage, so the schema already documents it ('格式为 工具名:目的。'). The description adds no parameter-level information, which is acceptable given the high coverage; baseline 3 applies.

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 states a specific verb and resource ('删除本地保存的凭据' / delete locally saved credentials) and the parenthetical 'log out, sign out' reinforces intent. It is clearly distinguishable from the login siblings (start_qr_login, complete_qr_login, get_login_status), though it does not name any of them explicitly.

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?

There is no when-to-use or when-not-to-use guidance beyond the implied act of logging out. No alternatives (e.g. get_login_status to check state first) or prerequisites are mentioned, so the agent must infer all usage context.

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