add_get_delta_seconds_node

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 only states the add operation and provides conceptual background; it does not mention side effects on the blueprint, whether the graph is saved/compiled, idempotency, failure cases, or what the caller receives. An agent is left uncertain about the operation's footprint beyond the minimal verb.

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 one-line action is front-loaded, and the educational delta-time explanation is short and relevant. Args, KB reference, and example are compactly organized. The Ch.5 background is somewhat ancillary but does not bloat the entry.

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 simple two-parameter add-node operation, the description includes the required blueprint path example, the optional position, a KB pointer, and an invocation example. Since an output schema exists and complexity is low, the main missing pieces are prerequisites and failure modes, which are not critical for a basic successful call.

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 coverage is 0%, so the in-description Args section is essential. It clarifies blueprint_name with an '/Game/MCP_Test/BP_Example' path example and describes node_position as 'Optional [X, Y] graph position', adding meaning the schema's types and titles alone do not convey. It could detail coordinate conventions further, but it meaningfully compensates for the schema gap.

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?

Opens with a specific verb+resource: 'Add a "Get World Delta Seconds" node.' This unambiguously names the exact node and distinguishes it from the many sibling add_*_node tools. The rest reinforces the purpose without confusing it with other graph operations.

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 useful context for when delta time is relevant ('Used to make movement frame-rate independent... Always multiply movement values by DeltaSeconds'), but it never explicitly states when to use this tool over alternatives or when not to use it. Among the long sibling list, no alternatives or exclusions are mentioned; the intended selection case is implied mainly by the tool name.

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