iec_logout

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

With no annotations, the description carries the full behavioral burden. It does disclose one meaningful trait — the saved session is forgotten, i.e. persisted state is cleared — but says nothing about idempotency, server-side vs local logout, or failure behavior when no session exists.

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?

A single short sentence with the action front-loaded; nothing is wasted. The colon-mid-sentence phrasing ("here: forget the saved session") is slightly awkward but the key information lands 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, no-return-value session-teardown tool, the description covers what an agent needs to select and call it. The remaining gap — whether logout is local-only or invalidates the server session — is minor for a tool of this complexity.

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, so the baseline is 4. There is no argument surface for the description to explain, and it correctly avoids inventing one.

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 states a specific verb+resource ("Sign out of IEC") that is unambiguous and naturally distinguished from the iec_login and iec_session_status siblings. It stops short of explicitly naming those siblings or the session boundary it operates on, so it clears the bar without full sibling differentiation.

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?

There is no when-to-use or when-not-to-use guidance, and no alternative is named. An agent can infer it should be called to terminate a session, but nothing in the text states prerequisites (e.g. whether an active session is required) or consequences of calling it twice.

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