add_set_view_target_with_blend_node

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

No annotations are provided, so the description must fully disclose behavioral traits. It explains the node's purpose but does not mention that this modifies the blueprint graph, any side effects (e.g., the player's view changing), or prerequisites like needing a PlayerController blueprint. For a mutation tool, the lack of explicit disclosure about modifying the blueprint 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 well-structured with a clear purpose statement, a contextual paragraph, an Args section, a KB reference, and an example. It is not overly verbose and front-loads the main action. The Args list is compact and informative.

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 that the output schema exists (as indicated by the context signals) and schema descriptions are absent, the description compensates well by covering use cases, parameter meanings, and an example. It does not mention prerequisites (e.g., existing blueprint) or return values, but the output schema likely covers the latter. The KB reference adds further depth. Overall, it is complete enough for an agent to invoke the tool 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 compensate. It lists all five parameters with meaningful explanations: blueprint_name is the target Blueprint (PlayerController), blend_time is duration in seconds, blend_func has allowed values enumerated, blend_exp is the exponent for cubic/ease functions, and node_position is [X, Y] coordinates. This adds substantial value beyond the schema's bare types and defaults.

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 the tool's function: 'Add a SetViewTargetWithBlend node to switch cameras smoothly.' It provides specific use cases (e.g., entering a treasure room activates a security camera) that distinguish it from other node-adding tools like add_set_actor_location_node. The verb and resource are 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?

The description gives clear context for when to use the tool (camera switching in cutscenes or security cameras) and even mentions typical input ('The New View Target input is usually a Camera Actor reference'). However, it does not explicitly mention alternatives or when not to use it, such as comparing to a simple SetViewTarget node or stating exclusions. The use-case context is strong but lacks direct comparison to sibling tools.

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