execute_python

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

The description discloses that the tool runs arbitrary code with access to the full unreal module, which implicitly signals it can perform broad operations. However, it does not elaborate on potential side effects, dangers, or what happens after execution (e.g., return values, errors), and there are no annotations to fill this gap.

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 short sentences, front-loaded with the core verb and resource, and includes only essential details. There is no wasted wording or repetition of schema information.

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 tool with a single parameter and no output schema, the description is largely complete: it states what the tool does and the environment context. It does not explain return values or error behavior, but given the simplicity and the explicit mention of arbitrary code execution, it covers the primary needs for an agent to use it 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 schema coverage is 100% with the 'code' parameter described as 'Python code to execute in the editor'. The description adds meaningful context by noting access to the full 'unreal' module, which informs what the code can reference, going beyond the schema's generic description.

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 tool executes arbitrary Python code in the Unreal Editor's Python environment, using a specific verb and resource. It distinguishes itself from siblings like execute_console_command by specifying Python, and the addition of 'full unreal module' clarifies its scope of access.

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 implies this is the general-purpose tool for running Python in the editor, but it does not explicitly state when to prefer it over alternatives or provide exclusions. There is no mention of alternative tools or use cases, leaving the agent to infer its role from the name and context.

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