blender_ai_generate_model_sync

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

With no annotations, the description carries the full burden and does disclose key traits: blocking synchronous behavior, combined generate+poll+optional import, and return on completion. But it omits the timeout behavior implied by max_wait (what happens when the limit is exceeded?) and the default side-effect that auto_import=true modifies the Blender scene by default. These are material gaps for a blocking tool.

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?

Three short sentences, each earning its place: purpose and sync mode, combined workflow, and return behavior. Front-loaded with the core function and zero filler or repetition of schema content.

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?

The workflow is well covered for a 7-parameter wrapper and the schema is complete, but with no output schema the vague 'Returns the final model when done' leaves the return structure unspecified (file path? object name? status object?). The timeout/error behavior gap also remains. Adequate but incomplete for an agent that must handle failure cases.

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 coverage is 100%, so the baseline of 3 applies; the schema already documents every parameter with a description and 3 enums. The description adds little per-parameter meaning — only 'optional import' maps to auto_import — so there is nothing it needs to compensate for.

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 verb and resource ('Generate a 3D model') and immediately adds the defining trait — '(synchronous)' — that separates it from the async blender_ai_generate_model sibling. The phrase 'Combines generate + poll + optional import in one call' explicitly defines its scope relative to the generate/poll workflow tools, so an agent can distinguish it without opening any schema.

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 conveys clear usage context: this is the one-call blocking alternative to a generate-then-poll workflow, with optional import. However, it never explicitly names the alternatives (blender_ai_generate_model, blender_ai_model_status) nor states when to prefer the async path (e.g., long generations, parallel work). Clear context, but no explicit exclusions.

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