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

With no annotations, the description carries the behavioral burden. 'Revoke the current session' clearly indicates a state-changing action scoped to the current session. It does not elaborate on side effects such as whether subsequent authenticated requests will fail until a new session is started, but for a zero-parameter logout the core effect is conveyed.

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 five-word sentence with no filler, no duplication of the schema, and no unnecessary context. It is front-loaded and every word contributes meaning.

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 tool with no parameters and no output schema, the description is mostly complete: an agent can invoke it with an empty object and understand the action. The only omitted context is the post-condition behavior, such as token invalidation and the need to re-authenticate afterward.

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?

There are zero parameters and the schema is empty, so the description cannot be expected to add parameter-level detail; per baseline, a 0-parameter tool receives a 4. The phrase 'current session' confirms the operation targets the authenticated context rather than requiring an explicit identifier.

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 uses a specific verb ('revoke') and a precise resource ('the current session'), making the operation unambiguous. It also naturally distinguishes from auth_start/auth_verify, which establish or verify sessions, and from api_key_revoke, which revokes API keys rather than the current 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 intended use is implied by the action: call this when the user wants to end the current session. However, there is no explicit when/when-not guidance or reference to alternatives, such as clarifying that it does not revoke API keys or terminate other members' sessions.

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