import_generated_asset

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

No annotations are provided, so the description carries full burden for behavioral transparency. It only states that the tool imports an asset and returns success status. It does not disclose potential side effects, error conditions, permission requirements, or what happens if the asset does not exist. This is insufficient for a mutation tool.

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 with four short sentences, front-loading the purpose. The parameter explanations are clear but slightly verbose; still, every sentence adds value. It is well-structured for quick comprehension.

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 the tool's complexity (3 parameters, no output schema, no annotations), the description covers the basic purpose and parameter usage but lacks behavioral transparency and completeness. It does not explain the return value format beyond 'Return if the asset has been imported successfully', which is vague. More details on errors and expected outcomes are needed.

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?

With 0% schema description coverage, the description compensates by explaining each parameter: name is 'The name of the object in scene', task_uuid and request_id are linked to their respective modes. This adds meaning beyond the schema's raw titles and defaults. However, it lacks details like allowed formats or uniqueness constraints.

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: importing an asset generated by Hyper3D Rodin. It distinguishes itself from sibling tools like generate_hyper3d_model_via_text and generate_hyper3d_model_via_images, which handle generation instead. The verb 'import' is specific to this action.

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 explicit guidance on parameter selection: 'Only give one of {task_uuid, request_id} based on the Hyper3D Rodin Mode!' It implies the tool should be used after generation, but does not explicitly state when not to use it or what alternative approaches exist. The context is clear enough for most use cases.

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