ue_execute_python

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

Annotations already flag destructiveHint=true. The description adds that it is the most powerful tool, has access to all editor APIs, and that print() is used for output. This provides useful behavioral context beyond annotations, though it could mention potential side effects like scene modification.

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?

Two sentences, each earning its place. No redundant information. Front-loaded with the core purpose and immediately followed by key capabilities and usage guidance.

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 complexity and destructive potential, the description explains input, output mechanism, and when to use it. The presence of an output schema reduces the need to describe return values. Slight lack of safety warnings, but overall complete enough.

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 description coverage, the description fully compensates by explaining that the 'code' parameter takes Python code, has access to editor APIs, and that print() returns output. This adds meaning 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 it executes Python code in the UE5 editor, specifies access to the 'unreal' module and editor APIs, and explicitly contrasts with sibling tools by calling itself the most powerful tool to use when no specific tool exists.

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?

Explicitly says 'use it when no specific tool exists for your operation,' giving clear guidance on when to prefer this tool over alternatives. Lacks explicit exclusions but the context of sibling tools makes the usage context clear.

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