run_python_script

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

No annotations are provided, so the description must disclose behavioral traits. It only notes the prerequisite and omits any mention of potential side effects, permissions, or safety implications of executing arbitrary code in the editor, leaving a significant transparency 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 a single, front-loaded sentence that efficiently communicates both purpose and prerequisite without any wasted words.

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?

Executing arbitrary Python code is a high-complexity, potentially destructive operation, yet the description provides no information about return values, error handling, or effects on the editor. With no output schema and no annotations, the description is insufficient for an agent to safely predict behavior.

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 covers 100% of parameters with a description that mirrors the tool description ('Python code to execute in the UE Editor'). The description adds no additional meaning about expected format, limits, or execution behavior, so the baseline of 3 is appropriate.

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 specifies 'Execute Python code in the Unreal Engine Editor,' giving a precise verb and resource. The resource distinguishes it from sibling tools like execute_console_command, which handles console commands rather than Python scripts.

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 usage by stating it executes Python code, but it does not explicitly compare with alternatives or state when not to use it. It mentions a prerequisite (Adastrea-Director running), but that is not a full usage guideline.

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