logout

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

There is a direct contradiction: the description says it terminates the ABAP session and clears cookies, with a warning that the server process must be restarted, while annotations state readOnlyHint=true and destructiveHint=false. This contradiction makes the description unreliable in combination with the annotations.

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 front-loaded with the action, immediately followed by the WARNING, and then the relevant alternative. It has no filler and says the critical side-effect first.

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 tool, the description sufficiently explains the action, the irreversible consequence, and the correct alternative. Even without an output schema, this is enough to invoke the tool 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 takes zero parameters and the input schema is empty, so there are no parameter semantics to explain. The description correctly does not add unnecessary parameter details, and the baseline for no parameters is acceptable.

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?

States a specific action and resource: "Terminate the ABAP session and clear its cookies." It also differentiates from the sibling tool `dropSession` by pointing out that `dropSession` only releases the session, and it gives a clear sibling pointer.

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 tells the agent when not to use it (if you only need to release the session) and names the alternative `dropSession`. The WARNING also makes the irreversible consequence clear, so the agent can decide whether logout is appropriate.

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