dropSession

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

Annotations declare readOnlyHint=true and destructiveHint=false, which is somewhat contradicted by the description's mention of clearing cache and releasing locks—though not a direct contradiction. The description adds valuable behavioral context: it releases held locks server-side and forces a re-login on the next call, which goes beyond the annotations. However, the readOnlyHint=true annotation is misleading for a cache-clearing operation, so the description's transparency is partially undermined by the annotation mismatch.

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, compact sentence that front-loads the primary action and includes the key side effects in parentheses. Every word earns its place; no fluff or repetition.

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 no output schema, the description covers the essential behavior: what it clears, what side effects occur (locks released, re-login needed). It could be slightly more explicit about when to call it (e.g., after a session error), but the core information is present.

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 is trivially complete. The description adds no parameter details because none are needed. Baseline 4 for zero-parameter tools 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 clearly states the action ('Clear the local session cache') and the resource ('session cache'), with a specific verb. It distinguishes itself from siblings like login/logout by describing the session lifecycle effect, though it doesn't explicitly name a sibling alternative.

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 usage context: it's for clearing a session cache and releasing locks, and notes the next call logs on again. However, it doesn't explicitly state when to use this vs. alternatives like logout or unlockAll, leaving the agent to infer the appropriate scenario.

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