ue_call_function

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

With no annotations, this description should disclose side effects, since calling arbitrary Blueprint functions can mutate world state or execute destructive operations. It only states what the function does, not possible consequences or error conditions, 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?

Two sentences, front-loaded with the core action, and includes a helpful example list and a pointer to ue_describe_object. No 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?

For a tool that can invoke arbitrary functions, it provides a good high-level overview and schema coverage is complete. However, it lacks return value description, error handling, and side-effect warnings, which are important for a potentially destructive tool with no output schema.

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 already covers all three parameters with descriptions, so the baseline is 3. The description adds no extra parameter meaning beyond noting the function must be Blueprint-callable.

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 identifies the tool as invoking Blueprint-callable functions on UObject instances, with concrete examples (actor methods, engine utilities, custom Blueprint functions). This distinguishes it from sibling tools like ue_set_property and ue_execute_console_command.

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 prescribes a specific workflow: use ue_describe_object first to discover available functions. It does not explicitly mention when not to use it or name direct alternatives, but the guidance is clear and actionable.

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