logout

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

Beyond the destructiveHint and readOnlyHint annotations, the description discloses irreversible side effects, the need to re-enter a PIN for trading, clearing of website cookies and shared token caches, and the separate browser profile copy. This gives the agent a full picture of consequences the annotations alone do not convey.

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?

Every sentence earns its place: the purpose is front-loaded, the mandatory user confirmation is highlighted first, and each subsequent sentence explains a necessary consequence or parameter behavior. It is long but tightly packed with safety-critical information.

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 destructive, three-parameter, no-output-schema tool, the description fully covers prerequisites, parameter choices, hidden side effects, and irreversibility. Nothing an agent needs to safely invoke it is missing.

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?

While schema coverage is 100%, the description adds significant meaning: scope 'main' also clears website cookies and token cache, 'trading' ends the session at Stockbit, and remove_browser_profile deletes a second copy of credentials. This goes well beyond the schema's short parameter descriptions.

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 opens with the specific, actionable statement 'Clear stored Stockbit credentials from this machine', establishing the exact verb and resource. It further differentiates the tool from siblings like login by describing scopes and destructive effects.

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?

It gives explicit usage guidance: 'ASK THE USER FIRST, then call with confirm: true' and explains what each scope does. It does not explicitly contrast with sibling login, but the purpose and invocation conditions are clear enough for an agent to decide when to call it.

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