import_generated_asset_hunyuan

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

With no annotations, the description carries the full burden of transparency. It mentions the return value ('Return if the asset has been imported successfully') but does not clarify side effects, error handling, or whether the import modifies or replaces existing assets. The lack of detail on failure modes or permissions leaves behavioral ambiguity.

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 and well-structured, with a clear purpose statement followed by a simple parameter list and return hint. No unnecessary words or redundant information.

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 description explains the tool's purpose, usage timing, and return value, which is adequate for a straightforward import operation. It does not elaborate on exception cases or specific outcome details, but given no output schema, it sufficiently conveys the expected result.

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 description provides explicit meanings for both parameters: 'name: The name of the object in scene' and 'zip_file_url: The zip_file_url given in the generate model step.' Since the schema offers no descriptions, this covers 100% of parameters, adding necessary semantic clarity.

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 tool's purpose: 'Import the asset generated by Hunyuan3D after the generation task is completed.' It specifies the resource (asset) and action (import) and differentiates from siblings like generate or poll by focusing on importing a generated asset.

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 provides temporal guidance ('after the generation task is completed') and ties the zip_file_url to the generation step ('given in the generate model step'), which implies when to use this tool. It does not explicitly mention alternatives, but the context is sufficient for typical usage.

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