Clear session token

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

The description discloses a behavioral trait beyond the only annotation (openWorldHint: false): the env fallback EREBRUS_BEARER_TOKEN continues to apply until process exit. This is crucial for the agent to understand the tool's effective scope and potential side effects, and it is not present in any structured field.

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 action and includes the important env fallback caveat without any fluff. It is appropriately sized for a zero-parameter tool.

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 simple logout tool with no parameters, no output schema, and minimal annotations, the description covers the core operation and a key edge case. It is fully adequate for an agent to invoke 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 has zero parameters, which qualifies for the baseline score of 4. No parameter description is needed, and the schema coverage is trivially 100%.

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?

Description states 'Clear the MCP session PASETO', which is a specific verb+resource combination. It clearly distinguishes from siblings like auth_import_token (importing a token) and auth_status (checking status). The title 'Clear session token' aligns perfectly.

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?

No explicit alternatives are named, but the tool's purpose as a logout action is self-evident. The description adds useful usage context by noting that the EREBRUS_BEARER_TOKEN env fallback still applies until process exit, implying this tool may not fully deauthenticate if that env var is set.

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