ue_add_component

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

The description discloses that the tool recompiles the Blueprint after adding the component, which is a notable side effect. However, it does not mention other behavioral aspects such as whether the operation is reversible, prerequisites, or error conditions. Compilation is a key behavioral trait beyond the schema.

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 concise: a one-sentence action statement followed by bullet-point parameter explanations. Every sentence adds value, and the structure is front-loaded with the core purpose.

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?

The description covers the main action and parameter details adequately for a simple tool. However, it lacks information about return values (e.g., success/failure) and prerequisites (e.g., the Blueprint must exist). Given no output schema, these missing details slightly reduce completeness.

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 description provides clear examples for each parameter: blueprint_path (e.g., '/Game/MyGame/Blueprints/BP_Door'), component_class (e.g., 'StaticMeshComponent'), and name (explanation). Since the input schema has no descriptions (0% coverage), the description fully compensates by adding meaning and context.

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 'Aggiunge un componente a un Blueprint e lo ricompila', which specifies the action (adds a component) and the resource (Blueprint), distinguishing it from sibling tools like ue_create_blueprint or ue_add_variable.

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 implies usage for adding components to Blueprints, but does not explicitly state when to use this tool vs alternatives, nor provide conditions or exclusions. No when-not or alternative tool names are mentioned.

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