BlenderMCP

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions access rights and downloadability as prerequisites, which is helpful, but fails to describe key behaviors such as what 'import' entails (e.g., file format, destination), error handling, or rate limits. This leaves significant 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: the first states the purpose, the second lists parameters, and the third covers returns and prerequisites. It is front-loaded with the main action, though the parameter listing could be integrated more smoothly.

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 complexity of a download/import operation, no annotations, no output schema, and low schema coverage, the description is incomplete. It lacks details on what 'import' means, the output format beyond a success/failure message, error conditions, or integration with sibling tools, making it inadequate for full understanding.

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 type. However, it does not provide examples or format details, such as what a valid UID looks like.

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 verb 'download and import' and the resource 'Sketchfab model by its UID', making the purpose specific and understandable. However, it does not explicitly differentiate from sibling tools like 'search_sketchfab_models' or 'import_generated_asset', which would require more detailed comparison.

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 by mentioning 'model must be downloadable and you must have proper access rights', which provides some context for prerequisites. However, it lacks explicit guidance on when to use this tool versus alternatives like 'search_sketchfab_models' or 'import_generated_asset', leaving the agent to infer based on the action needed.

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