m2_session_reset

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

With no annotations, the description carries the full burden of behavioral disclosure. It clearly warns that resetting discards ALL session state and explicitly states that rings and definitions from earlier calls no longer exist. This accurately conveys the destructive nature of the operation, which is the most critical behavioral trait for an agent to know.

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?

Three sentences with zero waste: the first sentence states the action and its primary consequence, the second gives usage triggers, and the third reinforces the permanent loss of prior state. It is front-loaded and every sentence earns its place.

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, self-contained reset tool with an output schema, the description covers the action, when to use it, and the key side effect. Nothing an agent needs to decide whether to invoke this tool is missing.

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 and the schema is empty, so there are no parameter semantics to clarify. Baseline 4 applies because nothing is missing; the description naturally requires no parameter discussion.

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 'Restart' with a clear resource ('the Macaulay2 kernel') and explicitly states the core effect: discarding ALL session state. It is immediately distinguishable from siblings like m2_evaluate or m2_interrupt because it focuses on kernel lifecycle, not computation or interruption.

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 provides concrete when-to-use guidance: 'before starting a fresh line of computation' or 'whenever the session seems corrupted.' It does not explicitly name alternatives or exclusion cases, but the use cases are clear enough to route an agent correctly, especially with sibling names providing context.

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