add_instanced_static_mesh_component

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

With no annotations, the description carries the burden of explaining behavior. It discloses that static_mesh_path can be set later and that attach_to_root controls root vs child attachment, which is helpful. However, it does not mention side effects such as whether the Blueprint asset is saved/compiled or what output is produced, leaving a meaningful transparency gap for a mutating operation.

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 organized with intro, context, note, args, KB link, and a concrete example. It is not padded; the only mildly non-essential part is the Ch. 19 background, which still supports purpose clarity.

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?

All parameters are documented, defaults are clarified, an invocation example is present, and a KB reference is provided for deeper context. Because an output schema exists, the lack of return-value detail in the description is acceptable; remaining gaps are minor (e.g., whether the Blueprint needs to be loaded first).

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%, and the Args section fully compensates by giving clear meaning to every parameter: blueprint_name's role, component_name's panel location, static_mesh_path's optionality, and attach_to_root's True/False behavior. This exceeds what the bare schema provides.

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 defines a clear action: 'Add an Instanced Static Mesh component to a Blueprint,' naming both the resource and the component type. It gives useful domain context (ISM for many copies, HISM for LOD), but it does not explicitly distinguish this tool from sibling component-adding tools like add_component_to_blueprint.

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 context that helps an agent decide when ISM is appropriate, and it explicitly notes HISM as an alternative for meshes with LOD. It stops short of enumerating sibling tools or giving a clear 'when-not-to-use' rule, but the guidance is nonetheless meaningful.

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