logout

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

Annotations declare readOnlyHint=false, consistent with a credential-deleting operation. The description adds genuine context beyond the annotations by specifying the credentials are LOCAL, which tells the agent this is a client-side clean-up rather than a server session revocation. It does not state whether the user must re-authenticate afterward, keeping it short of a 5.

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 carrying the full meaning, with the bilingual synonyms in parentheses aiding disambiguation. Nothing wasted.

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 no explanation. For a no-argument, single-purpose logout tool the description covers what is needed; it only lacks a note on post-logout state or prerequisites.

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 the baseline is 4; the description has no parameter semantics to add and does not need to.

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: it deletes locally stored credentials, which is exactly what 'logout' means and distinguishes it from siblings like get_login_status and start_qr_login. Clear enough that an agent can tell it apart from the login-flow tools, though it doesn't name any of them.

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 name and description — call this when the user wants to sign out — but there is no explicit when-to-use statement, no prerequisite (must be logged in), and no mention of how it relates to get_login_status or the QR-login tools. Adequate for such a simple, self-evident operation, but no guidance is actually provided.

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