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: it's a download/import operation (implying mutation), mentions access rights, and indicates success/failure messaging. However, it lacks details on side effects (e.g., where files are saved, format), error handling, or rate limits, leaving gaps for a mutation 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?

The description is appropriately sized with three sentences: purpose, parameters, and behavioral notes. It's front-loaded with the core action. While efficient, the parameter section could be integrated more smoothly, and the prerequisites might be better phrased, but overall it avoids unnecessary verbosity.

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 the tool's complexity (download/import mutation), lack of annotations, no output schema, and 0% schema coverage, the description is moderately complete. It covers purpose, parameters, and some prerequisites, but misses details on output format, error cases, and integration with sibling tools, making it adequate but with clear gaps.

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?

The schema description coverage is 0%, so the description must compensate. It adds meaning by explaining that 'uid' is 'The unique identifier of the Sketchfab model', which clarifies the parameter's purpose beyond the schema's basic string type. However, it doesn't provide format examples, length constraints, or where to find the UID, leaving some ambiguity.

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 action ('Download and import') and resource ('a Sketchfab model by its UID'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'search_sketchfab_models' or 'import_generated_asset', which would be needed for a score of 5.

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 prerequisites ('model must be downloadable and you must have proper access rights'), but doesn't explicitly state when to use this tool versus alternatives like 'search_sketchfab_models' for discovery or 'import_generated_asset' for other import operations. It provides some guidance but lacks clear alternatives.

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