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 of disclosure. It clearly states the destructive effects by enumerating what is cleared (objects, selections, settings) and uses 'Reinitialize' to indicate a reset to a default state. However, it does not explicitly mention irreversibility or lack of confirmation prompts, which could be valuable for a destructive operation.

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 sentence that directly states the action and its effects, with no unnecessary words. It is front-loaded and immediately communicates the tool's core function, which is ideal for an agent that needs to quickly parse and understand the 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?

For a parameterless tool with a clear destructive action, the description provides all necessary information needed for invocation. The presence of an output schema covers return values, so the description adequately captures the tool's behavior without missing critical details.

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 has zero parameters, so the description is not required to explain parameter meanings. The baseline of 4 applies since the tool takes no arguments, and the description does not need to compensate for any schema gaps.

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 'Reinitialize' and identifies the resource (PyMOL) along with the exact scope of its effect (clearing all objects, selections, and settings). This clearly distinguishes it from sibling tools that operate on specific items, making the purpose unambiguous.

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 does not provide any guidance on when to use this tool versus alternatives, such as selectively deleting objects or starting fresh in another way. While the purpose implies usage, there is no explicit 'use when' statement or pointer to other tools, leaving the agent without clear decision-making support.

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