disconnect

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

The description goes beyond the destructiveHint annotation by clarifying that this only forgets a local stored credential, does not delete data in TaskLite, and does not revoke the key server-side. This is exactly the nuance an agent needs to avoid overestimating the tool's blast radius.

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 short sentences carry the main action, the use cases, and the critical non-effects without wasted words. The most important scoping statement comes first.

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 parameterless local credential-disconnect tool, the description is complete. It communicates what happens locally, what does not happen remotely, and when the agent should invoke it, leaving no meaningful gap.

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 little to document. The description adds no parameter details, but none are needed; the baseline for an empty schema is appropriately high.

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 names the specific action—disconnecting this machine from TaskLite by forgetting the stored credential—so an agent clearly knows what operation it performs. It also distinguishes this local disconnect from other account-management tools like connect or 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?

The description gives explicit when-to-use guidance: before connecting a different account or to revoke local access. It does not explicitly name alternative tools to use instead, but the context makes the intended situation clear.

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