execute_python

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

Without annotations, the description must disclose all behavioral traits. It mentions that the `unreal` module is pre-imported and how to return data (set `result`), but it does not describe error handling, side effects, execution environment constraints, or permission requirements.

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 long, with the main purpose in the first sentence and behavioral notes in the second. Every sentence contributes value, and there is no unnecessary 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?

Given the tool is a Python executor with an output schema (per context signals), the description provides sufficient information for core usage. It lacks details on environment persistence or timeouts, but for a simple execution tool it is largely complete.

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?

Although the schema has 0% description coverage for the `code` parameter, the description adds crucial context: it explains how to use the parameter to return structured data (set `result` variable) and that `unreal` module is available. This significantly enhances understanding beyond the raw schema.

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 arbitrary Python code inside the running Unreal Editor.' This is a specific verb (execute) and resource (Python code in Unreal Editor), and it distinguishes itself from sibling tools which are all targeted operations (e.g., save, get assets).

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 no guidance on when to use this tool vs. alternatives (e.g., for automation vs. direct manipulation via other tools). It does not mention prerequisites, when not to use it, or how it compares to sibling tools that achieve similar effects.

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