ms_add_variable

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

With no annotations, the description must carry the full behavioral burden. It usefully discloses the UE 5.7+ version requirement, the uniqueness constraint on names, and the allowed data types, but it does not mention mutation side effects, permissions, whether the graph must be saved afterward, or what happens on duplicate names.

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 front-loaded with the action and resource, then adds concise context and a clean Args section. Every sentence contributes useful information without repetition or filler.

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 three-parameter mutation tool with an output schema and no annotations, the description gives enough detail to call it correctly: purpose, required parameters, type values, and uniqueness constraint. It remains slightly incomplete because it does not address when to choose this tool over related alternatives or whether saving is required.

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%, so the description must fully compensate. It documents all three parameters, including the unique-name constraint for name, the complete allowed type list (Float, Int32, Bool, Trigger, Audio, Time, String), and that default_value is optional and passed as a string.

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 verb and resource: adding a graph variable to the current MetaSounds builder. It distinguishes the concept from generic node addition by explaining that graph variables store state readable/writable by Get/Set Variable nodes, but it does not explicitly differentiate itself from siblings such as ms_add_variable_node or ms_add_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 explains what a graph variable is but gives no guidance on when to use this tool versus alternatives like ms_add_node, ms_add_variable_node, or ms_set_default. It also omits any prerequisites beyond the UE 5.7+ requirement.

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