logout

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

No annotations are provided, so the description carries the full burden. It discloses that the tool revokes the connection, deletes saved login, and causes hosted tools to disappear until next login. This is meaningful behavioral context beyond a simple 'log out' statement. It doesn't mention side effects like whether other machines are affected, but for a logout tool this is reasonably transparent.

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?

Three sentences, each earning its place: the action, the behavioral effects, and the usage trigger. Front-loaded with the verb and resource. No fluff.

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 zero-parameter logout tool with no output schema, the description covers the action, effects, and when to use it. It could mention whether the user will be prompted for confirmation or whether it affects other sessions, but those are minor gaps. The description is complete enough for an agent to invoke it correctly.

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, so the schema is trivially complete. The description adds context about what the operation does, which is more than needed. Baseline 4 for zero params is appropriate.

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 states the verb 'Log out' and the resource 'Mockzilla cloud on this machine', and distinguishes it from the sibling 'login' by describing the effect (revokes connection, deletes saved login). It also mentions hosted tools disappearing until next login, which adds clarity about the scope of the operation.

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 explicitly says when to call it: 'when the user asks to log out or to switch organization or access level.' This provides clear usage context and implicitly distinguishes it from login and other tools. It doesn't name alternatives explicitly, but the condition is specific enough.

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