reset

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

The description indicates a destructive action (clearing session and snapshots) but lacks details on reversibility, side effects, or authorization needs. With no annotations provided, the description carries the full burden, and it is adequate but not comprehensive.

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, clear sentence with no unnecessary words. It is front-loaded and concise.

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 zero parameters and the existence of an output schema, the description is mostly complete. However, it does not mention what the output will be (e.g., success confirmation) or any prerequisites, but the output schema likely covers return values.

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 cannot add meaning beyond the schema. The baseline of 4 is appropriate since the schema already fully covers the empty parameter list.

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') and the resource ('current session back to empty state, including all snapshots'). It distinguishes itself from sibling tools like 'restore_snapshot' (which restores a specific snapshot) and 'clearance' (likely unrelated).

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?

No explicit guidance on when to use this tool versus alternatives. For a zero-parameter tool, the need is less critical, but mentioning use cases (e.g., 'Use when starting a new session' or 'Avoid if you need to preserve snapshots') would improve clarity.

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