Clear stored Clio credentials

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

Annotations indicate destructive (destructiveHint=true) and idempotent (idempotentHint=true). Description adds context: it only deletes the local token file, not affecting remote sessions or revoking the token. No contradictions with 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?

Three sentences, each serving a purpose: first states core action and scope, second clarifies a critical limitation, third addresses additional context for remote connector. Front-loaded, no fluff.

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?

Given no parameters, no output schema, and annotations, the description fully covers what the tool does, its limitations, and when to use alternatives. Complete for a simple logout tool.

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?

Tool has 0 parameters, so schema coverage is 100%. With no parameters to document, the description need not add parameter details. Baseline score 4 for zero-parameter tools.

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 title 'Clear stored Clio credentials' and description 'Deletes the encrypted token file for the shared account' clearly state the specific action and resource. Among siblings like clio_authenticate and clio_auth_status, it unambiguously serves as the logout counterpart.

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?

Explicitly states when to use (to clear local credentials) and when not: it does not revoke the token on Clio's side and does not clear remote per-user sessions. Provides alternatives: use Clio's Developer Applications screen for full revocation, or disconnect the connector in Claude for remote sessions.

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