execute_python

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While it mentions arbitrary code execution and access to the full `unreal` module, it does not disclose potential side effects (e.g., modifying assets, saving packages, or crashing the editor) or error handling behavior. This is a significant gap for a tool with such broad capabilities.

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 sentences, front-loaded with the core purpose, and contains no fluff. Every word earns its place, making it highly concise and well-structured.

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 relative simplicity (single parameter, no output schema, no annotations), the description is minimally adequate. It explains the purpose and scope but lacks details on return values, error behavior, or how to retrieve output (e.g., print statements). For a generic code execution tool, this is arguably sufficient, but it could be more informative for a broader audience.

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 covers 100% of the parameter (code), including its description ('Python code to execute in the editor'). The tool description itself adds no additional meaning beyond what the schema already provides, so it stays at the baseline for high schema coverage.

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, with access to the full `unreal` module. This specific verb+resource clearly distinguishes it from sibling tools that perform specific operations like applying materials or running tests.

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 tool is for custom logic not covered by other, more specific tools, but it does not explicitly say when to use it versus alternatives or when not to use it. No exclusions or alternative recommendations are provided, so the guidance is minimal but not misleading.

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