portal_sitzung_loeschen

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

With no annotations, the description carries the full behavioral burden. It discloses the client-side scope, which is a useful behavioral detail, but does not mention whether authentication is required, what happens if no session exists, or any side effects beyond clearing the local session. The client-side qualifier provides some transparency but leaves gaps.

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 concise sentence that front-loads the core action and scope, with no filler. It is appropriately sized for a simple tool and every word contributes meaning.

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?

Though an output schema exists, the description omits essential context such as parameter semantics and usage guidelines, and does not clarify behavior when the session is absent. The simple tool could be used with just the name, but the description alone leaves the agent under-informed for correct invocation.

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 schema has zero description coverage for portal_id, and the tool description does not explicitly explain the parameter. However, the phrase 'eines Portals' implies that portal_id identifies which portal's session to delete, providing a minimal semantic link. The description does not add detail about format or how to obtain the ID.

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 tool deletes the saved session of a portal, using the specific verb 'Loescht' and the resource 'gespeicherte Sitzung eines Portals'. It also clarifies the client-side logout scope, which distinguishes it from sibling tools like portal_login and anmeldedaten_entfernen.

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 provides no explicit guidance on when to use this tool versus alternatives, nor does it mention exclusions such as not affecting stored credentials. The clause 'Logout auf Client-Seite' implies a client-side operation but does not specify when to invoke it (e.g., after portal_login).

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