BlenderMCP

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

With no annotations provided, the description carries full burden and does well: it discloses that the tool generates AND imports, mentions built-in materials, normalized size requiring rescaling, and success/failure messaging. It doesn't cover rate limits, authentication needs, or error specifics, but provides substantial operational context beyond basic functionality.

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 efficiently structured: purpose statement first, key behavioral notes (materials, scaling), then parameter details with clear formatting. Every sentence adds value—no redundancy or fluff. The parameter section uses bold and lists for readability while maintaining brevity.

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 no annotations, 0% schema coverage, and no output schema, the description does an excellent job covering purpose, behavior, and parameters. It mentions the return is a success/failure message. Minor gaps: no explicit error handling, no details on Blender import specifics (e.g., scene placement), and sibling context could be more explicit. Still, highly complete for the complexity.

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 0% schema description coverage, the description fully compensates by explaining all three parameters: it clarifies the mutual exclusivity of input_image_paths vs input_image_urls based on Hyper3D Rodin mode, specifies absolute path requirement and list wrapping, and details bbox_condition as optional 3-int list controlling [Length, Width, Height] ratio. This adds crucial meaning not in the bare schema.

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 the specific action: 'Generate 3D asset using Hyper3D by giving images of the wanted asset, and import the generated asset into Blender.' It distinguishes from sibling tools like 'generate_hyper3d_model_via_text' by specifying image-based generation, and from 'import_generated_asset' by including the generation step. The verb+resource+destination combination is precise and unambiguous.

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 clear context for when to use this tool: for generating 3D assets from images via Hyper3D and importing to Blender. It implicitly distinguishes from text-based generation (sibling tool 'generate_hyper3d_model_via_text') and from standalone import ('import_generated_asset'). However, it doesn't explicitly state when NOT to use it or mention all relevant alternatives like downloading existing models from Polyhaven/Sketchfab.

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