mne_reset_session

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

With no annotations provided, the description carries the full burden. It explicitly discloses that the operation is 'Irreversible' and specifies the scope ('all loaded objects and figures'). This effectively communicates the destructive nature and what is cleared, though it could mention side effects like unsaved state, but the coverage is solid for a reset action.

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 two compact sentences, front-loaded with the action 'Clear all loaded objects and figures' and followed by the impact 'Irreversible.' Every word earns its place with no fluff.

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 simple tool with no parameters and an output schema that presumably defines return values, the description covers the essential facts: action, scope, and irreversibility. Nothing critical is missing for an agent to select and invoke this tool correctly.

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 there is nothing to explain beyond what the schema already conveys (an empty object). The baseline for 0 params is 4, and the description adds no irrelevant param details.

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 a specific verb 'Clear' with a clear resource: 'all loaded objects and figures from the session'. It states the outcome ('starting fresh') and is distinct from all sibling tools, which focus on analysis or loading operations. This unambiguously identifies the tool's function.

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 phrase 'starting fresh' clearly implies the intended use case: when the user wants to reset the session state. It does not explicitly mention alternatives or when not to use it, but for a simple reset tool, this is sufficient context. The tool's uniqueness among siblings (no other reset tool) further clarifies usage.

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