add_vector_subtract_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. It explains the node's math behavior and shows a call example, which is helpfulERO. However, it doesn't disclose side effects such as requiring an existing blueprint, whether the blueprint is modified in place, or any permissions/save implications. For an 'add node' tool this is a moderate gap, but the additive nature is implied by the name.

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 short and well-organized: purpose, mathematical explanation, args, KB link, and example. Every line contributes meaningful information and nothing is redundant. The most important details are front-loaded, making it easy for an agent to scan.

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 node-addition tool, the description is largely complete. It includes the operation semantics, parameter meanings, a knowledge base reference, and an example call. The output schema is marked as present, so return values are covered externally. It only lacks explicit handling of edge cases (e.g., invalid blueprint name) or behavior when node_position is omitted, but these are not critical given the simple scope.

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?

The input schema has 0% description coverage, so the description is the only source of parameter meaning. It lists blueprint_name as 'Blueprint name' and node_position as 'Optional [X, Y] graph position', plus an example that illustrates the blueprint path format. This adds value but is minimal—it doesn't explain coordinate system, units, or default behavior of node_position, leaving some ambiguity for an agent.

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 what the tool does: adds a Vector-Vector subtraction node, and clarifies the operation with "Subtracts element-wise." It also includes a concrete formula (movement = destination - start_point) that differentiates it from sibling vector node tools like add_vector_add_node and add_vector_multiply_node.

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 clear usage context via the Ch.14 example, indicating when this node is useful (e.g., computing movement from destination and start_point). However, it never explicitly mentions when not to use it or names alternatives, so it stops short of full exclusion guidance.

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