session_clear

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

With no annotations, the description carries the full burden. It discloses that it clears a cached session and that re-authentication may be needed, which implies a destructive effect on the session. However, it doesn't mention permissions, whether other sessions are affected, or whether this also invalidates associated tokens, so it is only partially 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 very brief and to the point: a single-core statement, a usage condition, and a returns note. Every sentence serves a purpose and there is no filler, making it highly concise and well-structured.

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 zero-parameter tool with a simple return (confirmation message), the description covers the operation, when to use it, and the return format. It could additionally mention side effects or relation to sibling session tools, but given the low complexity, it is sufficiently complete.

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 schema already fully documents the input (none). The description correctly avoids inventing parameter details. A baseline of 4 is appropriate because no parameter explanation is needed.

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 action: 'Clear the cached session for document operations.' This identifies a specific verb and a resource (cached session for document operations), which makes the purpose clear. It doesn't explicitly contrast with siblings like jwt_clear_token, but the resource scope gives enough differentiation.

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 conditions: 'Use this if you need to re-authenticate or if the session is causing issues.' This is a clear context for when to invoke the tool. However, it doesn't name alternatives or provide exclusions, such as 'use jwt_clear_token for token-specific issues,' so it stops short of a 5.

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