dropSession

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

No annotations are provided, so the description must fully disclose behavioral traits. It states that the tool keeps STATEFUL mode and preserves object locks, which is helpful. However, it does not mention whether the operation is safe to repeat, what exactly gets cleared, or any side effects. For a cache-clearing tool, this is adequate but not fully 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 a single sentence that immediately states the core action and the important behavioral detail. Every word earns its place; there is no redundancy. It is optimally concise and front-loaded.

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 the simple nature of the tool (no output schema, one optional parameter, low complexity), the description covers the essential behavioral distinction from sibling tools (resetSession, etc.). It does not explain return values or error handling, but for a cache clear operation, this is acceptable. However, a brief note on what the tool returns (e.g., success message) would improve completeness.

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 coverage is 100% (one parameter 'connection' is described in the schema). The description does not add any additional meaning about the parameter or its usage. Since the schema already explains it, the description provides no extra value for parameter semantics.

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 local session cache'. It also adds the key differentiator: 'keeps STATEFUL mode so object locks still work', which distinguishes it from sibling tools like resetSession. This meets the criterion of specific verb+resource with sibling 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 implies when to use this tool (when you want to clear cache without disrupting locks), but it does not explicitly state when not to use it or provide alternatives. There is no mention of context like 'use this instead of resetSession if you need to preserve locks'. Thus, usage guidelines are only implied.

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