LogoffLeftoverSession

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

With no annotations supplied, the description carries the full burden and does so: it discloses that every lock held by the session is released, that only a credential-free logoff is transmitted, that the session record is deleted afterwards, and that it must run outside batch mode.

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?

Four short clauses, all informative, with the action and its effects front-loaded. The bracketed [read-only] [session] tags are low-cost but slightly redundant given the prose that follows.

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 single-parameter, no-output-schema tool, the description covers the action, the post-conditions (locks released, record deleted), the transport behavior (credential-free logoff only), and the execution constraint. Nothing needed to invoke it correctly is missing.

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?

There is a single parameter with 100% schema description coverage, so the schema already explains what the handle is and where it comes from. The description adds no further constraints or format detail beyond the schema, so baseline 3 applies.

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 verb and resource ("Logs off a leftover SAP session") plus scope ("any role"), which clearly separates it from read-only siblings such as ListLeftoverSessions. It never names the sibling that produces the handle, however, so the differentiation is implicit rather than 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?

Gives clear operational context: the tool targets leftover sessions and "Runs outside batch mode," which tells the agent when it is callable. There is no explicit statement of when not to use it or which alternative to pick for a live/active session.

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