Create 3D model generation task

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

Annotations indicate readOnlyHint=false (write operation) and destructiveHint=false, which align with the description. The description adds value by clarifying that the tool is asynchronous ('Returns a task ID for polling'), which is a key behavioral trait not captured by annotations. No contradictions are present.

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 two sentences, but the first sentence is essentially a repeat of the title ('Create 3D model generation task'). The second sentence is valuable and concise. Structurally, it is front-loaded but could be tighter by merging the two sentences. Overall, it is brief and to the point.

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 complexity (9 parameters, async task creation) and the absence of an output schema, the description is minimally adequate. It mentions the task ID and polling, which are critical, but does not explain how to use the task ID (e.g., with get_task_status), nor does it cover whether the tool supports both text-to-3D and image-to-3D (implied by 'image' and 'image_url' parameters). Some implicit context is provided by sibling tools, but direct completeness is lacking.

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 schema description coverage at 56%, the tool description does not compensate by explaining any parameters. It makes no mention of required parameters (e.g., 'prompt') or optional ones (e.g., 'seed', 'image', 'format'). The schema itself provides partial descriptions, but the tool description adds no semantic value beyond stating the service (Tripo3D), which is already a model default.

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 it creates a 3D model generation task using Tripo3D, with a specific verb ('creates') and resource ('3D model generation task'), and mentions the return value ('task ID for polling'). This distinguishes it from other creation tools like 'create_image' or 'create_video' by specifying the domain (3D) and the asynchronous nature.

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 no explicit guidance on when to use this tool versus alternatives (e.g., when to use text-to-3D vs image-to-3D, or when to use a different model). It does not specify prerequisites, such as having an active Tripo3D account, nor does it clarify when not to use it. The mention of polling implies asynchronous usage but is implicit.

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