clear-session

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

With no annotations, the description carries the burden of disclosing behavior. It clearly states the destructive nature ('Clear all data') and the scope ('current research session') with 'resetting completely,' which conveys irreversibility. However, it does not specify whether other persisted data (e.g., saved papers) are affected, nor any confirmation requirements, leaving a small gap.

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, concise sentence that front-loads the action and scope, with no extraneous words. It is appropriately terse for a zero-parameter 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?

The tool is simple with no parameters and no output schema. The description fully explains the action and its effect, making it complete for the given complexity. It doesn't describe a return value, but that's not essential for a clearing operation.

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 input schema is empty with zero parameters, so there are no parameter details to explain. The baseline for zero parameters is 4; the description adds no parameter semantics but none are needed, as the tool operates without input.

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 the specific verb 'clear' against the resource 'current research session,' and explicitly states 'all data' and 'resetting completely,' making its function unambiguous. It distinguishes itself from sibling tools like get-current-session by indicating a destructive reset rather than a view operation.

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 the tool is for resetting the session when a clean slate is needed, but it provides no explicit guidance on when to use it versus alternatives, nor any warnings about not using it if data preservation is needed. The context signal is clear, but no exclusions are described.

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