get_render_target_cube_info

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds real value beyond that by disclosing that the operation reads metadata only and touches no pixels, and by spelling out the returned fields since no output schema exists.

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 in one tight sentence, then a compact structured returns list. Slightly verbose with the inline field enumeration, but every element is informative, especially given the absence of an output schema.

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?

With no output schema, the description usefully compensates by documenting the full return shape, and it covers purpose, scope, and read semantics. The only gap is routing to sibling info tools, which for a simple single-param read tool is minor.

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% for the sole render_target_path parameter, with the schema itself providing the example path format. The description adds no extra syntax or format detail beyond the schema, so the baseline 3 applies.

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 (Read metadata) and a precise resource (UTextureRenderTargetCube asset), then enumerates the metadata fields returned. Naming the cube asset type inherently distinguishes it from siblings like get_render_target_info (2D) and get_render_target_2d_array_info.

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?

Gives clear context and an explicit exclusion: 'Metadata-only, no pixel readback' tells the agent this tool is not for reading pixel data. It stops short of 5 because it never names the alternative tool to use when pixel readback is actually needed.

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