create_scene_component

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

With no annotations provided, the description carries the full burden of behavioral transparency. It does disclose that the result is a Scene Component Blueprint with Transform and hierarchy capabilities, which is useful. However, it does not clarify side effects or boundaries, such as whether orbit behavior is actually implemented, whether the asset is compiled/saved, or what happens with invalid parameters.

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 into a definition, book context, bulleted use cases, Args, a KB reference, and an example. It is longer than minimal but every section earns its place and the core definition is front-loaded.

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?

Given the sparse input schema and no annotations, the description covers the essential what, when, and how: asset type, use cases, parameter formats, and an example call. An output schema exists, so return-value documentation is not needed. The main remaining gap is the unaddressed relationship to closely related sibling tools.

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 Args section must compensate, and it does: all three parameters are described, the variables parameter has an explicit JSON structure, and the example call clarifies usage. The description adds meaning absent from the schema, though it does not fully detail allowed types or validation rules.

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 line 'Create a Scene Component Blueprint (has Transform - location/rotation/scale)' clearly identifies the verb and resource, and the Transform detail distinguishes it from actor components. However, it does not explicitly distinguish this tool from close siblings like create_actor_component or create_circular_movement_component, so it falls one step short of 5.

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 use cases list (orbiting attachments, floating damage numbers, auras, socket attachment points) provides clear context for when to call the tool. But it gives no exclusions or alternatives, and the orbiting use case overlaps with the sibling tool create_circular_movement_component, leaving routing ambiguous.

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