qobrix_sign_out

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

With no annotations provided, the description takes full responsibility and details side effects: 'calls the Authorization Server /disconnect (deletes the minted Qobrix API key and clears AS tokens/vault)', 'clears this user's local encrypted session vault', and 'Other users' vaults on this MCP process are not affected.' This is comprehensive behavioral disclosure.

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 sentences front-load the core action and then add necessary behavioral detail. No wasted words; every clause adds value about scope, process, or exclusions.

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?

The tool is simple (no params, no output schema), and the description covers purpose, usage modes, side effects, and exclusions. It fully equips an agent to decide when and how to invoke it.

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 is empty with zero parameters, so the baseline is 4. The description adds meaningful context about the sign-out operation's effects, though it doesn't need to explain parameters.

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 explicitly states 'Sign out of Qobrix (Mode C only)' – a specific verb and resource. It details the operation's scope and distinguishes it from sibling tools like qobrix_sign_in and qobrix_whoami by describing full session revocation.

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 explicitly scopes usage to 'Mode C only' and explains that 'In Mode A/B there is no interactive session to clear.' This provides clear when-to-use and when-not-to-use context, though it does not name an alternative tool.

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