bp_sync_from_engine

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

With no annotations, the description does real work: it reveals the underlying engine call, the conditional upsert into the blueprint_nodes_scraped table, and the read-only behavior when update_db is false. It omits error/failure behavior and any engine-connection prerequisite, but the core side-effect profile is disclosed.

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?

Front-loaded with the purpose sentence, then a mechanism sentence, then structured Args/Returns blocks. Slightly verbose in repeating the list_blueprint_functions detail, but nearly every sentence carries 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?

For a five-parameter ingestion/sync tool with no annotations, the description covers mechanism, side effects, parameters, and defaults. The Returns block is somewhat redundant given an output schema exists, and sibling disambiguation is absent, but the definition is otherwise sufficient to invoke correctly.

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 carry the load, and it documents all five parameters with meaning and defaults (audio_only, update_db, filter, class_filter, limit). It explains what each filter acts on (function or class name), which the bare schema does not.

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?

States a specific verb and resource — sync the Blueprint function catalogue from the running UE5 engine — and explains the mechanism (enumerating BlueprintCallable UFunctions via list_blueprint_functions). It does not, however, distinguish itself from near-siblings like ms_sync_from_engine or bp_scan_blueprint, leaving the agent to infer the difference.

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 implies usage (fetch engine function data, optionally persist it) and describes the update_db branch, but never states when to choose this over bp_scan_blueprint or the equivalent ms_ sync tool, nor prerequisites such as an established ue5_connect session. Usage is inferable but not explicit.

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