bp_call_function

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states that a Blueprint function is executed, but does not describe side effects, whether the function may mutate editor or runtime state, required permissions, error behavior, or whether the call is synchronous or asynchronous. For a tool that executes arbitrary user-defined functions, this is a significant 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?

The description is appropriately short and front-loaded: the main action appears first, followed by a compact Args section. Every sentence is relevant, though the parameter explanations are minimal and could be slightly more informative without bloating the text.

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?

The tool has an output schema, so return values need not be described. However, with no annotations, two parameters, and 0% schema description coverage, the description is incomplete: it lacks usage guidance, safety considerations, and sufficient parameter detail for an agent to invoke it reliably. Given the power of executing arbitrary Blueprint functions, more context is needed.

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 description coverage is 0%, so the description must compensate. It briefly explains both parameters: 'function_name: Blueprint function name to call' and 'args_json: JSON string of function arguments.' This adds basic meaning beyond the bare schema titles, but it does not explain how to format the JSON to match the target function's signature or how to discover valid function names.

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 states a specific verb and resource: 'Execute a Blueprint function via the UE5 plugin.' This clearly distinguishes the tool from sibling tools like bp_compile_blueprint or bp_add_bp_node, which manipulate blueprints rather than invoking a function. However, it does not explicitly differentiate from other execution or runtime tools in the sibling list.

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 gives no guidance on when to use this tool versus alternatives. It does not mention prerequisites such as an active UE5 connection, whether the blueprint must be open, or what conditions make this tool preferable to siblings like ms_graph_to_commands or execute_waapi. Usage must be inferred entirely from the tool name and brief purpose statement.

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