logout-user

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

No annotations are provided, so the description must carry the burden. It clearly states the core behavior: logging out the current user. It adds nuance with 'currently authenticated', implying that it operates on an existing session. However, it does not disclose edge cases (e.g., what happens if no user is logged in) or whether tokens are invalidated, though these are not critical for such a simple operation.

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 sentence of five words: 'Log out the currently authenticated user.' It is front-loaded, clear, and contains no superfluous information. Every word 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 the tool's simplicity (no parameters, no output schema, no annotations), the description is fully sufficient. It clearly communicates the action and the target, leaving no meaningful gaps for an agent to select and 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 coverage is trivially 100%. Per the rubric, 0 params gets a baseline of 4 because there are no parameter semantics to clarify. The description adds no parameter information because none is needed.

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 action ('log out') and the resource ('the currently authenticated user'). This is specific and distinguishes it from sibling tools like login-user, get-current-user, and delete-user, which have different actions.

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 usage is implied by the action and resource: use this to end the current user's session. However, there is no explicit guidance on when to use vs alternatives, no mention of prerequisites like being authenticated, and no exclusions. This is minimal implied guidance.

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