add_anim_blueprint_variable

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

With no annotations, the description carries the full burden, yet it only says 'Add a variable'. It does not disclose whether the asset must be open, whether the change immediately mutates/saves the asset, how existing variables are handled, or any failure conditions.

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 compact and well organized: summary, Args, KB pointer, and example. The structure earns its place, though the incorrect example adds minor noise and the example repeats the variable name as the type.

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 four-parameter mutation with no annotations, the description is adequate: it identifies the target asset, parameter meanings, and a KB reference. It still omits side effects, naming constraints, and conflict behavior, leaving an agent to infer the full operational contract.

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%, so the Args section supplies meaning for all four parameters, including valid variable_type options and an example for variable_name. However, the example passes 'ExampleName' as variable_type, which contradicts the listed types and could mislead an agent; default_value is only glossed as 'Optional default value'.

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 opening sentence names a concrete action and resource: 'Add a variable to an Animation Blueprint' and adds the intended use ('for use in transitions/logic'). This clearly separates it from generic blueprint variable tools like add_blueprint_variable among the siblings.

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 phrase 'for use in transitions/logic' implies when the variable is needed, but the description never says when to prefer this tool over add_blueprint_variable or any other sibling, and it gives no exclusions or preconditions.

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