add_set_collision_profile_node

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly signals the additive mutation ('Add a node'), but it does not disclose side effects, prerequisites like blueprint/component existence, whether existing collision-profile nodes are replaced, or whether compilation is required. This is a notable gap for a mutation tool.

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 lead sentence, an Args list, a KB reference, and an example. It is not bloated, though the 'Common presets' line is slightly redundant with the profile_name allowed values and includes 'Custom' which is not in the allowed list.

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 four-parameter node-adding tool, the description covers the parameters, allowed values, and an example, and an output schema exists so return-value details are not required. However, it omits behavioral context such as prerequisites, error conditions, or what happens if the component or blueprint is invalid, leaving the description not fully complete for an agent operating without annotations.

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 must compensate, and it largely does. It explains all four parameters, enumerates the allowed profile_name values, notes node_position as optional [X,Y], and gives an example that illustrates the blueprint_name path format. This adds meaningful meaning beyond the bare schema.

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 a specific action—'Add a Set Collision Profile Name node for a component'—and identifies the resource and node type. However, it does not explicitly distinguish itself from related sibling tools like set_collision_settings or add_set_collision_enabled_node, so it stops short of full differentiation.

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 useful context about collision presets and their role in component trace/overlap responses, which implies when this tool is relevant. It does not explicitly state when to prefer this tool over alternatives or mention exclusion cases, leaving the routing decision mostly to inference.

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