reset_python_state

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

With no annotations, the description fully discloses behavior: what gets cleared (all user-defined names, including explicit imports), what is preserved (names starting with '_'), and the effect on the editor state. It also explains the relationship with exec_python_persistent.

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 three short sentences front-loaded with the core action, followed by specific exceptions (preserved names, cleared imports). Every sentence adds value with no redundancy.

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 the tool's simplicity (no parameters, no output schema), the description is completely adequate. It covers purpose, behavior, exceptions, and usage context without missing any essential information.

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 100% schema coverage. The description needs no parameter information, and it adds meaningful context about the operation's scope, meeting the baseline for no-param tools.

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 states the exact action: clearing user-defined names from UE Python's public globals dict. It specifies the verb 'clear' and the resource 'globals dict', and distinguishes from siblings like exec_python_persistent by explaining it pairs with that tool to wipe state.

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 explicitly says to use it 'to wipe accumulated state and start fresh without restarting the editor' and pairs it with exec_python_persistent. It implies when to use but lacks explicit 'when not to use' or alternatives beyond the pairing context.

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