Generate a 3D model

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the core function and limitation. Missing critical details such as async behavior (wait parameter), file saving requirement (save_to parameter), and URL expiration, which are crucial for correct usage.

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?

Two sentences, no filler. All information is front-loaded and directly relevant. Every word serves a purpose.

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 8 parameters and no output schema, the description is insufficient. It does not explain async behavior, parameter interactions, or output characteristics beyond the file format. The high schema coverage does not compensate for the lack of overarching 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 88%, meaning the schema provides adequate context for most parameters. The description does not add further parameter-level meaning beyond restating the format. Baseline score of 3 is appropriate given high coverage.

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?

Description clearly states 'Generate a 3D model (.glb) from a text prompt' with a specific verb, resource, and format. It explicitly distinguishes from image-to-3D, differentiating it from potential sibling tools such as generate_image.

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?

Description provides clear usage context: text-to-3D only, and explicitly rules out image-to-3D. However, it does not mention when to use this tool versus siblings like generate_image or generate_video, though the stated limitation provides implicit guidance.

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