system_logout

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

Discloses reliance on private attribute api._auth_configs and potential degradation. States it does NOT contact daemon or modify host config. Annotations already indicate non-read-only but description adds important caveats beyond annotations.

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?

Description is longer but well-structured with paragraphs for context, args, and returns. Every sentence adds value. Could be slightly more concise but not wasteful.

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 tool with 1 optional parameter and no output schema, the description covers purpose, behavior, parameter details, return format, caveats, and relations to siblings. Complete documentation.

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?

With 0% schema coverage, the description fully compensates: explains registry is optional, default clears all, passing a key clears only that entry, with note that key must match system_login and Docker Hub is cached under 'docker.io'. Adds meaning beyond schema.

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?

Clearly states the tool clears cached registry credentials from the in-memory Docker client. Distinguishes from system_close and system_reconnect which also clear but by discarding the client entirely. The verb 'clear' is specific to the resource 'cached registry credentials'.

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?

Explains when to use: to drop in-memory cache without contacting daemon or touching config. Mentions alternatives (system_close/system_reconnect) and explains they discard the client. Lacks explicit 'when not to use' but context is sufficient.

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