disconnect_sundhedClose the browser and forget the session, ensuring no data is stored. Next use requires a new MitID login.
Closes the browser and forgets the session. Nothing is stored, so the next use needs a new MitID login.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds meaningful behavioral context beyond annotations: it states that the browser is closed, the session is forgotten, nothing is stored, and a new MitID login is required next time. This fully clarifies the side effects and future session behavior, which 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?
Two short, direct sentences with no filler. The most important behavioral fact (session termination) is front-loaded, and the consequence (new MitID login) follows immediately. Every sentence earns its place.
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 zero parameters, no output schema, and clear side-effect disclosure, the description is complete for an agent to invoke this tool correctly. The only needed context—what happens and what follows—is explicitly stated.
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 input schema has zero parameters, so the baseline is 4. The description appropriately explains the operation without needing to document parameter semantics. Nothing is missing here.
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 as ending the session: 'Closes the browser and forgets the session.' This unambiguously differentiates it from siblings like connect_sundhed, session_status, and the various read-only get_* tools. Specific verb and resource are both explicit.
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 implies the correct context—use when the agent is done with the session or needs to log out—and distinguishes it from session_status and connect_sundhed. It does not explicitly state exclusions or alternative conditions, but the purpose is self-evident from the logout semantics.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.