Create 3D model generation task

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

Annotations (non-readOnly, non-idempotent) are consistent with the description stating a creation action. The description adds that it uses Tripo3D and returns a task ID, but does not disclose side effects, authorization needs, or polling behavior details. With annotations present, the bar is lower, but the description adds minimal context beyond the annotations.

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 short but contains a redundant phrase ('Create 3D model generation task' repeated). It is not optimally structured and could be more concise without losing information.

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?

With 9 parameters (1 required) and no output schema, the description only mentions returning a task ID. It does not explain how to poll for results, the role of optional parameters, or how they affect the output. This is insufficient for a complex tool.

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 56% (5 of 9 params have descriptions). The description does not document any parameters or add meaning beyond what the schema already provides. It fails to compensate for undocumented parameters like model, format, quality, and image_url.

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 that the tool creates a 3D model generation task using Tripo3D and returns a task ID for polling. This distinguishes it from siblings like create_image or create_video. However, the first sentence is slightly redundant, repeating 'Create 3D model generation task' twice.

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?

No guidance is provided on when to use this tool compared to siblings (e.g., create_image, create_video). There is no mention of prerequisites, when not to use it, or alternatives.

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