exec_unreal_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. It discloses the action and the required environment but does not mention potential side effects of arbitrary code execution, error behavior, or response content. While the execution action itself is inherently transparent, valuable behavioral context is missing.

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 concise and well-structured: a one-sentence purpose, a necessary prerequisite, and a simple Args list. Every sentence earns its place without 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?

For a single-parameter execution tool, the description covers the essential purpose, the environment requirement, and the parameter meaning. Since an output schema exists, return values need not be described. It could add a warning about destructive potential, but the description is otherwise sufficient for correct selection and invocation.

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?

Schema coverage is 0%, so the description must compensate. The Args section defines 'code' as 'Python code to execute in Unreal Editor,' which gives necessary meaning. However, this largely restates the tool's purpose and adds no additional detail about expected formatting or multi-line input.

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 'Execute Python code in the running Unreal Editor,' specifying the verb (execute), resource (Python code), and context (running Unreal Editor). This distinguishes it from sibling read-only introspection tools like list_unreal_instances and get_class_overview.

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 provides a clear prerequisite: 'Requires Unreal Editor to be running with Python Remote Execution enabled,' along with setup instructions. It does not explicitly mention when to use this tool over alternatives or list exclusions, so it stops short of full guidance.

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