ue_exec_python

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

No annotations are provided. The description discloses it executes arbitrary Python and mentions the 'result' variable, but lacks details on side effects, error handling, or security implications. It gives some transparency but not full.

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 relatively concise, with the purpose stated in the first sentence. It includes a separate Args section. A bit more brevity could be achieved, but overall it is 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 complexity of arbitrary code execution and no output schema, the description should explain the return mechanism (result variable) and output format. It does mention 'result' but does not specify the return value type or behavior, leaving some gaps.

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?

With 0% schema coverage, the description adds meaningful context for the only parameter 'code' via an example, showing how to assign the return value. This compensates well for the lack of schema 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 it executes arbitrary Python code in the Unreal editor, using the verb 'esegue' and specifying the resource. This distinguishes it from sibling tools that perform other actions like saving, opening levels, or managing actors.

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?

It mentions 'escape hatch' implying advanced use, and lists available modules, but does not explicitly state when to use this tool over alternatives or provide exclusion criteria. Some guidance is present but not comprehensive.

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