blender_ai_generate_model

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

With no annotations, the description carries the full disclosure burden. It adds useful context—external service, API-key requirement, two input modes—but omits whether the call is asynchronous, what it returns, and how to track completion. For an AI generation tool with a `_sync` sibling and a `model_status` tool, these are central behavioral facts.

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 concise and front-loaded with the core action, followed by capability and prerequisite. Each sentence earns its place, though the brevity leaves out important workflow details an agent would need.

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 five parameters, no annotations, no output schema, and a sibling set that includes `_sync` and `model_status`, the description should explain the asynchronous workflow and expected return value. It doesn't, so an agent cannot reliably drive the generation call to completion.

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?

All five parameters are already described in the input schema, including enums and defaults, so the description doesn't add meaning beyond the structured data. The text-to-3D/image-to-3D distinction is already captured by the prompt and image_path schema descriptions.

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 states a specific action—generate a 3D model via Hyper3D Rodin AI—and names two input modes: text-to-3D and image-to-3D. However, it doesn't differentiate this tool from the sibling `blender_ai_generate_model_sync`, which is likely the synchronous counterpart, so clarity stops short of full sibling differentiation.

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 explicit when-to-use or alternative-routing guidance is provided. The description only mentions the API key prerequisite, but doesn't tell an agent when to choose this async version over `_sync`, or how to check progress via `blender_ai_model_status`. Usage context is left entirely to inference.

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