import_generated_asset

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

Mentions return value indicates success. No annotations provided, so description carries burden. Lacks details on side effects, error behavior, or authorization needs.

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?

Concise sentences with clear front-loading of purpose, followed by parameter details and a usage rule. No extraneous text.

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?

Covers parameters and return type. No output schema, so description mentions success check. Could be improved by noting behavior if generation task is not complete.

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% coverage, but description explains each parameter's purpose (name as object name, task_uuid and request_id with their sources) and adds critical constraint mutual exclusivity. Fully compensates for missing schema descriptions.

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?

Clearly states 'Import the asset generated by Hyper3D Rodin', specifying verb and resource. Distinguishes from sibling tools like import_generated_asset_hunyuan by naming the model provider.

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?

Provides explicit guidance on using task_uuid vs request_id based on mode, and warns to give only one. Does not explicitly state prerequisites or when not to use, but the context is implied.

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