revoke_auth_session

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

With no annotations provided, the description carries the burden of behavioral disclosure. It does this well by specifying the JWT limitation, the API key capability, and the need for a Proof account with PROOF_API_KEY configured. It does not mention irreversibility or error behavior, but the core behavioral constraints are transparent.

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 well-structured: it leads with the core action, then gives the critical JWT/API key distinction, then the necessary access setup. The ACCESS section is somewhat verbose but each sentence provides useful information for successfully calling the 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?

Given there is no output schema and only one parameter, the description covers the essential operational context: what the tool does, how authentication affects behavior, and what environment setup is required. It does not describe return values, but for a revoke operation this is a minor omission.

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 already documents session_id as 'Session ID to revoke' with 100% coverage. The description adds only that the session is 'specific' and 'by ID,' which does not meaningfully exceed what the schema provides. Baseline 3 is appropriate.

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 clear verb and resource: 'Revoke a specific authentication session by ID.' It is immediately distinguishable from sibling tools like list_auth_sessions and get_session because it specifies the revoke action and the targeting by ID.

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 strong contextual guidance, including the JWT/API key distinction and the explicit note that start_login does not open this tool. It does not name alternative tools for when to use them, but it clearly communicates the access prerequisite and the key restriction on revoking the current session.

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