Clear Stored Aukro Credentials

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description adds real value by specifying that credentials are removed from both memory and disk and that the server falls back to anonymous mode. It does not clarify whether subsequent calls fail or prompt for login, a minor gap.

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, front-loaded with the action and complete with scope and resulting state; nothing redundant.

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?

Adequate for a zero-required-parameter mutation with full annotation coverage, but it omits the practical consequence of logging out — that protected tools like aukro_my_account or aukro_place_bid will subsequently fail — which an agent would want before calling 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?

Schema coverage is 100% and the single parameter's own description already explains that removeDiskFile=true deletes the saved file on disk. The description adds the memory-versus-disk distinction at a high level but no extra detail on the flag, so 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?

States a specific verb (clear) plus the exact resources removed (session cookies and OAuth2 tokens) and the resulting state (anonymous mode), which distinguishes it cleanly from aukro_login_interactive and aukro_auth_status.

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?

Implies usage — you call this when you want to drop credentials — but never explicitly says when to use it versus aukro_auth_status (inspection) or aukro_set_credentials (replacement). No prerequisites or warnings about re-authentication.

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