create_render_target_cube

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

Annotations cover the safety profile (destructiveHint=true, idempotentHint=false), and the description adds genuinely useful context: it saves to disk, and re-running deletes and rebuilds the asset deterministically. That re-run/destroy note is the key behavioral disclosure an agent needs before calling. It omits permission/auth requirements, keeping it below 5.

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?

Front-loads the purpose, then behavior, then format values, then the return shape via a compact Returns block. Dense but every clause earns its place; minor redundancy in restating the InitAutoFormat default twice.

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?

For a mutating creation tool with no output schema, the description supplies the return shape inline, the format enumeration, size/format derivation, persistence and re-run semantics. Nothing an agent needs to call it correctly is missing.

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%, so the baseline is 3, but the description adds real meaning beyond the schema by enumerating the accepted format aliases ('B8G8R8A8'/'BGRA8', 'FloatRGBA'/'RGBA16F', 'RGBA32F') which the schema does not list, plus the auto-derived default behavior. This materially improves correct invocation.

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?

States a specific verb and resource ('Creates a persisted UTextureRenderTargetCube') and pins the cube 6-face variant, which clearly distinguishes it from create_render_target_2d and create_render_target_2d_array. The parenthetical '(6-face cube render target)' removes any ambiguity.

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 explains the format and re-run behavior but never states when to choose this tool over the 2D or 2D-array siblings, and offers no when-not guidance. Usage is only implicitly derivable from the resource name.

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