BlenderMCP

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: the tool generates 3D assets with built-in materials, imports them into Blender, produces normalized-sized models requiring potential rescaling, and returns a success/failure message. However, it lacks details on permissions, rate limits, error conditions, or what 'import into Blender' entails operationally.

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 appropriately sized and front-loaded, with the core purpose in the first sentence. Additional sentences provide useful context without redundancy. The parameter section is clear but could be more integrated. Minor improvements could enhance flow, but overall it's efficient with zero wasted sentences.

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, no output schema, and 0% schema description coverage, the description provides basic context: purpose, parameters, and behavioral notes like normalized size. However, for a tool that generates and imports 3D assets, it lacks details on output format, error handling, Blender integration specifics, or dependencies, leaving gaps in completeness.

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 0%, so the description must compensate. It adds meaningful semantics: 'text_prompt' is described as 'A short description of the desired model in **English**,' and 'bbox_condition' as 'Optional... Controls the ratio between [Length, Width, Height] of the model.' This clarifies purpose and constraints beyond the bare schema, though it doesn't fully detail format (e.g., units for bbox_condition).

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 tool's purpose: 'Generate 3D asset using Hyper3D by giving description of the desired asset, and import the asset into Blender.' It specifies the verb (generate), resource (3D asset), technology (Hyper3D), and destination (Blender). It distinguishes from sibling tools like 'generate_hyper3d_model_via_images' by specifying text-based generation and from 'import_generated_asset' by combining generation and import.

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 implies usage context through statements like 'The generated model has a normalized size, so re-scaling after generation can be useful,' which suggests when this tool is appropriate. However, it lacks explicit guidance on when to use this tool versus alternatives like 'generate_hyper3d_model_via_images' or 'download_sketchfab_model,' and does not mention any prerequisites or exclusions.

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