gen_tripo_refine_model

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

No annotations are provided, so the description must disclose operational behavior, but it only says 'Submit a task' and gives an example. It does not state whether the operation is asynchronous, whether it spends credits, how confirm_spend affects execution, or how the resulting task is tracked.

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 and front-loaded: a purpose sentence, a KB pointer, and a concrete example. There is no filler, though the brevity does mean some behavioral information is left out.

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?

This is a generative pipeline tool with no annotations, and the description omits key context such as async behavior, cost/credit confirmation, task-status polling, and follow-up steps. The KB reference helps but shifts the documentation burden instead of making the tool definition self-sufficient.

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 needed to explain the parameters. The example clarifies that task_id should be a draft task ID and shows confirm_spend=True, but session_name is never explained, and no parameter detail beyond the bare schema is provided.

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 action ('Submit a Tripo refine_model task') and the resource ('legacy draft model task'), making it clear this is the refine step in the Tripo family. It does not explicitly contrast it with sibling generation tools, but the verb and 'refine' wording distinguish it well enough.

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 'for a legacy draft model task' and the example using task_id='draft-task-id' imply it is used after a draft job exists, and the KB reference points to broader family guidance. However, there is no explicit when/when-not guidance and no mention of alternatives such as gen_tripo_texture_model or gen_tripo_post_process.

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