disconnect

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

The description transparently discloses the tool's local-only scope, stating that it does not delete anything in TaskLite or revoke the key server-side. This aligns with the destructiveHint annotation (the stored credential is removed) while clarifying that no broader destructive effects occur.

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?

The description is concise and well-structured, consisting of two sentences that convey all necessary information without redundancy or extraneous detail.

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 the simplicity of the tool (no parameters, single action), the description fully covers what it does, when to use it, and its limitations. It leaves no gaps that would prevent an agent from using it correctly.

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 has zero parameters, so there is nothing to describe. Per the rubric, a baseline of 4 is appropriate when no parameters exist. The description does not need to add parameter semantics.

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 description clearly states the tool's purpose: disconnecting the machine from TaskLite by forgetting the stored credential. It uses a specific verb ('disconnect') and resource ('machine from TaskLite'), and distinguishes it from server-side actions. This differentiates it from sibling tools like 'connect' and 'login'.

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?

Explicit guidance is provided: 'Use before connecting a different account, or to revoke local access.' This clarifies when the tool should be invoked and contrasts with server-side revocation, leaving no ambiguity about its intended use.

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