clear_session

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

The description details the destructive nature (unloads state) and preserves uploaded files, going beyond the destructiveHint annotation. No contradiction—it accurately reflects the tool's behavior.

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?

Extremely concise: one sentence for purpose, one list of what is unloaded, one note on preservation, and one warning. No wasted words, 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?

Given no input parameters and an output schema, the description fully covers the tool's effect on state, preservation policy, and usage constraints. It is complete for an agent to decide on invocation.

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 no parameters, so the description correctly avoids parameter discussion. The baseline for 0 parameters is 4, and the description provides sufficient context for the tool's operation.

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 tool's purpose: resets model and simulation state. It lists specific items unloaded (model, schema, results, migration report, weather file) and explains that uploaded files are preserved, distinguishing it from other tools like new_model or load_model.

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?

Explicit guidance on when to use (user asks to start over) and when not to use (tool errors); provides alternatives (retry or load_model). This is exemplary usage guidance.

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