gen_tripo_import_to_project

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

No annotations are present, so the description carries the full behavioral disclosure burden. It states the high-level operations but does not disclose that this mutates the project by importing assets, creating material instances or blueprints, or potentially overwriting existing assets. Side effects, permissions, and failure behavior are left to the KB reference.

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 compact, front-loaded with the core behavior, and each element earns its place: the one-line action, the KB anchor, and a concrete callable example. There is no filler or 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?

For a tool with 9 parameters, 0% schema description coverage, and no annotations, this description is too thin. It provides a useful example and KB pointer, but an agent cannot reliably call it correctly without external documentation about parameter semantics, prerequisites, and side effects. The output schema reduces the need to describe return values but does not compensate for the missing parameter guidance.

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 description coverage is 0%, so the description must compensate, but it only shows three parameters in an example (task_id, content_path, create_material_instance) without explaining their meaning. Ambiguous parameters like output_keys, target_folder, asset_name, and the interplay of overwrite_existing are not clarified.

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 names a specific sequence of actions—download a successful Tripo result, import it, and capture viewport evidence—with a clear resource and destination. This distinguishes it from siblings like gen_tripo_download_result by emphasizing the project import and evidence capture steps.

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 phrase 'successful Tripo task result' implies this should only be used after generation completes successfully, and the KB reference points to pipeline context. However, it never explicitly contrasts this with alternatives or states when not to use it, such as when only a raw download is needed.

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