create_experience_level_component

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

With no annotations, the description carries the burden of behavioral disclosure. It does disclose what will be created (the BP_ExpLevelComp with specific internals and defaults) and references a KB chapter for more detail. However, it does not mention potential side effects such as overwriting an existing asset, compilation outcomes, permission requirements, or any failure modes. This is a noticeable gap for a mutation tool without annotation safety hints.

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-structured: a one-sentence summary, bulleted list of created items, labeled argument list, KB pointer, and example. It front-loads the core purpose and every line adds information. Despite being longer than average, the format makes it scannable and free of fluff.

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 tool is moderately complex (creates a full component with macros and functions) and the description covers all inputs, the created structure, defaults, and a working example. It lacks explicit mention of prerequisite conditions (e.g., an open project, Unreal version) and does not describe the output/return value, but an output schema exists (per context signals) which reduces that burden. Minor gaps prevent a 5.

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 schema provides only names and default values with no descriptions (0% coverage), but the description compensates fully. It defines each parameter ('name: Component Blueprint name', 'max_level: Maximum number of levels', 'xp_per_level: XP required for each level up' with default pattern, 'folder_path: Content browser folder'). It also gives a concrete example invocation. This goes above and beyond the structured schema.

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 opens with a specific verb+resource: 'Create the complete experience/level-up Actor Component from Ch. 18.' It then enumerates exactly what is created (variables, macros, function), making the tool's purpose unambiguous. The detailed component list distinguishes it from generic creation tools like create_blueprint or 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 clearly states what the tool does and what inputs it takes, so an agent can infer when to use it (when wanting to create an experience/level-up component). It does not explicitly name alternative tools or state when NOT to use it, but the context is clear given the specialized function. This meets 'clear context, no exclusions'.

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