End the active BW session to force a fresh connection on the next call, while leaving other profiles untouched. Use after errors or to reset authentication.
Drop the current environment's BW session/client so the next call reconnects. Other profiles' sessions are left intact. Useful after errors or to force a fresh login.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral burden. It clearly discloses that the current session is dropped, the next call reconnects, and other profiles' sessions remain intact. This gives an agent a solid mental model of side effects.
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?
Two dense sentences with no filler. The action, scope restriction, and use cases are all front-loaded and each sentence adds meaningful 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 parameterless disconnect tool with no output schema, the description is complete: it states the action, the affected scope, the side effect on the next call, and the intended use cases. Nothing essential 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?
The tool takes zero parameters, and the schema fully covers that fact. With no parameters to document, the description appropriately adds no parameter-specific detail, and the baseline 4 applies.
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?
Description states a specific verb and resource: drop the current environment's BW session/client. It also clarifies scope by noting other profiles' sessions are left intact, which distinguishes it from environment-switching or other session-affecting 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?
Explicitly says when to use the tool: after errors or to force a fresh login. It could also mention when not to use it or explicitly contrast it with a sibling like environment switching, but the context is clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.