Log out of Banco General

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

With no annotations provided, the description carries the full burden, and it does disclose the destructive side effects: it deletes stored session data and Keychain credentials, and closes an in-progress login. It could add idempotency or failure behavior (e.g., behavior when already logged out), but the key side effects are clearly stated.

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 a single, well-structured sentence that names the primary effect first ('Deletes the stored session') and then the additional side effects. Every phrase earns its place; no filler or repetition.

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 that this is a parameterless logout operation with no output schema, the description is sufficient for an agent to invoke it correctly: it identifies the action and the important side effects. There is no missing information that would affect how the tool is called.

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 and schema coverage is nominally 100%, so there is nothing for the description to add about parameters. Baseline 4 is appropriate for a parameterless tool.

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 identifies the action ('Deletes', 'closes'), the resources affected (stored session, Keychain credentials, login in progress), and the overall purpose of logout. This distinguishes it from sibling tools like bg_session_status (which only checks state) and the various bg_login_* tools.

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?

Usage is implied rather than explicitly stated: the description makes it obvious that this tool ends a banking session and aborts in-progress logins. However, it does not explicitly say when to use it versus checking session state with bg_session_status, nor does it mention any preconditions such as being logged in.

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