remove_niagara_custom_hlsl_pin

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

The description adds 'rebuild its signature', which is a behavioral trait beyond the remove action, but it does not disclose other side effects like destructive nature or permission requirements. With no annotations, this is a modest addition.

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 a single concise sentence, but it omits important details like parameter roles, making it too brief for practical use. Still, it is front-loaded and efficient.

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 the tool has three required parameters with no schema descriptions and an output schema present, the description fails to explain parameter meanings or expected behavior, leaving significant gaps for correct invocation.

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% and the description provides no explanation for the three required parameters (pin_name, module_name, system_path). The user is left to infer their meaning from context alone.

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 uses the specific verb 'Remove' and identifies the resource as 'a pin from a Custom HLSL node', clearly distinguishing it from sibling tools like 'add_niagara_custom_hlsl_input' and 'rename_niagara_custom_hlsl_pin'.

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?

No guidance on when to use this tool versus alternatives such as 'remove_niagara_node_pin' or other pin removal tools. There is no mention of prerequisites, context, or exclusions.

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