set_widget_drag_drop

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

The description adds genuinely unusual behavioral disclosure beyond the annotations: the tool cannot mutate the property and it documents the exact return contract (set: false, has_drag_drop_property: false, note). However, it says nothing about the PIE refusal or the compile/disk-write hazard that justifies the destructiveHint=true annotation — that risk appears only in the force parameter's schema text, so the description leaves the annotations' safety claim unexplained rather than contradicting it.

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 key point (the capability does not exist and must be done in the BP graph) is front-loaded, followed by a compact structured Returns block. 'Honest gap report' is slightly editorial, but no sentence is wasted and there is no padding.

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?

With no output schema, the description correctly supplies the return shape, which is the main thing an agent needs to interpret results. Against a destructive, PIE-sensitive tool, though, it omits the refusal/force context that the schema's force field carries, so a reader of the description alone would not understand why the annotations mark it destructive.

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 100%, so the schema already documents all four parameters, including the important force/PIE behavior. The description adds no parameter-level meaning of its own, which is the expected baseline when the schema does the heavy lifting.

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 names the resource (widget drag/drop on a UWidget) and states the operative fact: there is no reflective UPROPERTY for DragDropOperationClass and the OnDragDetected/OnDrop delegates are not assignable, so the action cannot be performed here. The 'Returns' block makes the outcome explicit (set: false, has_drag_drop_property: false), so an agent can tell this is effectively a gap report rather than a working setter. It stops short of a clean verb+resource statement, but the negative purpose is unambiguous.

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?

Usage is only implied: 'The drag/drop behavior must be configured in the widget BP graph' points the agent at graph-authoring siblings (e.g., build_blueprint_graph, add_graph_node) without naming them. There is no explicit when-to-call or when-not-to-call statement for this tool itself.

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