import_generated_asset

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

Without annotations, the description carries full burden. It states the return value ('Return if the asset has been imported successfully'), but does not disclose potential side effects (e.g., scene modifications, error cases) or permission requirements.

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 concise: a clear purpose sentence, structured parameter list, and conditional note. Every sentence adds value with no redundancy.

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 or annotations, the description adequately covers purpose and parameters. It could improve by explicitly stating prerequisites (e.g., generation must be completed) and differentiation from Hunyuan sibling.

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 has 0% description coverage, so the description provides essential meaning: defines task_uuid for MAIN_SITE mode, request_id for FAL_AI mode, and name for scene object. It adds conditional exclusivity guidance far beyond schema titles.

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 imports assets generated by Hyper3D Rodin, using specific verbs and resource identification. It distinguishes from siblings like 'import_generated_asset_hunyuan' by specifying the source system.

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?

It provides clear guidance on parameter selection based on mode ('Only give one of {task_uuid, request_id}'), but lacks explicit when-not-to-use instructions or comparison to related tools like import_generated_asset_hunyuan.

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