bardo_session_revoke_current

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

The description adds context beyond the annotations by specifying that the current session is revoked and that future session-gated actions require re-authentication. This is consistent with the 'destructiveHint' and 'idempotentHint' annotations.

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 concise sentences with no unnecessary information. It is front-loaded with the action and provides essential follow-up context efficiently.

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?

The description covers the tool's action and aftermath but does not explain the optional session_token parameter. For a simple revoke tool, it is mostly complete, but the parameter omission leaves a gap.

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 input schema has a single optional parameter 'session_token' with no description, and the tool description does not mention or explain this parameter. With 0% schema coverage, the description fails to add any meaning for the parameter.

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 that the tool revokes the current session and mentions the need to re-authenticate. It does not explicitly differentiate from the sibling tool 'bardo_sessions_revoke_all', but the name and description are specific enough.

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 implies when to use the tool (to revoke the current session) and notes the consequence (need to login again). However, it does not provide guidance on when not to use it or compare to alternatives like revoking all sessions.

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