create_cubemap_from_texture

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

Annotations are all false (readOnlyHint=false, destructiveHint=false), giving no safety profile. The description says 'convert' but does not clarify whether the source texture is modified, whether new assets are created, or any side effects. It also doesn't mention input format requirements beyond 'equirectangular'.

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?

A single, well-constructed sentence with the verb and resource front-loaded, no filler, and all essential information present.

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 simple with one parameter and no output schema, but the description omits behavioral clarity (e.g., whether the original texture is preserved) and usage context relative to siblings. It adequately states the conversion but lacks end-to-end completeness for an agent to call it with full confidence.

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 has 100% coverage: the single parameter 'id' is described as 'Source equirectangular texture asset id', which is clear. The description adds no extra parameter semantics beyond what the schema provides.

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 clearly states the action ('Convert'), the input source ('an equirectangular texture'), and the exact outputs ('six face textures and a cubemap asset'). This specific purpose distinguishes it from siblings like prefilter_cubemap and convert_texture_asset without 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 implies usage (when you have an equirectangular texture needing a cubemap) but provides no explicit guidance on when to choose this tool over related siblings like prefilter_cubemap or convert_texture_asset. There are no when-not or alternative recommendations.

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