convert_hdri_to_cubemap

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

With no annotations, the description fully discloses behavior: spawning temporary actors, capture pipeline, cleanup of temp assets. It details the entire process, ensuring the agent understands side effects and safety.

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 with purpose, pipeline steps, and cleanup. It is detailed but not overly verbose. Slight improvement could be made by front-loading the most critical info, but overall effective.

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 no output schema, the description explains the output (static UTextureCube) and covers all inputs, process, and cleanup. It is comprehensive for the tool's complexity.

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 100%, but the description adds valuable defaults (e.g., dest_path defaults to source folder, dest_name to source basename plus _Cube), explains cube_size range, and lists compression options. This goes beyond the 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 explicitly states the tool converts a longlat-projection HDRI to a UTextureCube for use with SkyLight's SpecifiedCubemap slot. It distinguishes itself from siblings like import_texture and configure_texture by focusing on a specific conversion pipeline.

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 purpose clearly indicates use for SkyLight cubemap setup. It mentions being a 'SYNTHETIC bridge-side handler' but lacks explicit when-not-to-use guidance or alternative tools. The context is clear but could be stronger.

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