add_append_string_node

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

With no annotations provided, the description carries the full behavioral burden. It clearly states the action (adds a node), the node's purpose (string concatenation), and how the parameters feed into it. However, it does not disclose potential side effects, prerequisites like whether the blueprint must already exist, or whether the operation compiles or connects the node.

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 and front-loaded with the core action. It includes a brief use case, a concise argument list, a knowledge base pointer, and a realistic example. Each section earns its place without unnecessary verbosity.

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 node-addition tool, the description covers the essential context: purpose, parameters, example, and KB reference. The output schema exists, so not describing return values is acceptable. It lacks some guidance on when not to use it and does not mention required-versus-optional parameters, but the schema covers required fields.

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%, but the description compensates fully by explaining each parameter: blueprint_name is the target blueprint, string_a and string_b are the A/B pin defaults, and node_position is an [X, Y] graph position. This is significantly more meaningful than the raw schema property names 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 opens with a clear verb and resource: 'Add an Append (string concatenation) node,' and further explains it 'Combines two strings into one.' This is unambiguous and specific. However, it does not explicitly differentiate itself from sibling tools like add_format_text_node or add_print_string_node, though the operation is distinct enough by name.

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 provides a concrete use case: 'Used to build "Levelled up to " + CurrentLevel display string,' which implies when this tool is appropriate. It does not explicitly state when to use this tool versus alternatives, nor does it give exclusions or mention when another node type would be preferable.

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