Logout

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 usefully discloses that logout cleans up the current profile's session and OAuth pending files, but it omits auth requirements, server-side invalidation behavior, reversibility, and effects on other profiles.

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?

A single front-loaded sentence with no wasted words. The action and its cleanup scope are stated immediately.

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?

With an output schema present and full parameter descriptions in the schema, the description only needs to convey the operation's side effects; it does so by naming session and OAuth pending file cleanup for the current profile. It is largely complete for a simple logout tool, though auth-state and failure behavior remain unstated.

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?

Schema description coverage is 100%, so the schema already documents host, port, scheme, and profile. The description adds no parameter syntax or default behavior, making the baseline 3 appropriate.

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+resource ('退出登录') and adds the cleanup scope ('当前 profile 的 session 与 OAuth pending 文件'), which clearly distinguishes it from login/whoami siblings. An agent can identify this as the session-termination tool without opening the schema.

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?

Usage is implied by the verb: call it to end the authenticated session. It does not state explicit when-to-use conditions, what to use instead for querying the current user, or prerequisites such as needing an active login.

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