Clear the cached Sedis session token

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

The description discloses the full behavioral impact: it removes the token from memory and on-disk cache, and subsequent calls will omit the header until set_session is called. This goes beyond the annotations (readOnlyHint: false) by specifying exactly what gets destroyed and the side effects, which is exactly the kind of context needed.

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 two sentences, front-loaded with the core action ('Forget the locally-cached session token'), followed by the consequence and usage guidance. Every sentence earns its place with no redundant information.

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 has no parameters, no output schema, and clear annotations, the description completely covers the essential context: what it does, what happens to the token, how it affects subsequent calls, and when to use it. An agent can confidently invoke this tool based on the description alone.

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 baseline is 4. The description does not need to explain any parameter semantics, and it doesn't. It appropriately focuses on the tool's action and consequences.

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 purpose: 'Forget the locally-cached session token (removes it from memory and the on-disk cache)'. It uses a specific verb ('forget') and resource ('session token'), and makes the tool's action distinct from sibling tools like set_session.

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 explicit guidance on when to use this tool: 'Use it to sign out of the current session.' It also explains the behavioral consequence ('calls send no X-Api-Session header until you set_session again'), giving clear context. However, it does not explicitly mention when not to use it or contrast with alternatives beyond the implied set_session.

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