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 that the tool imports an asset after generation completion, implying a write operation that modifies the scene by adding an object. It mentions the return indicates success, but doesn't detail error conditions, permissions needed, rate limits, or what happens if the asset fails to import. The description adds some behavioral context but lacks comprehensive disclosure 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 four sentences that are front-loaded: the first states the purpose, the next three detail parameters and usage rules. There's minimal waste, though the last sentence about return could be integrated more smoothly. Overall, it's efficient and structured, earning a high score for clarity without 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 (importing generated assets with mode-specific parameters), no annotations, and no output schema, the description is moderately complete. It covers purpose, parameters, and basic usage, but lacks details on behavioral aspects like error handling, what 'successfully' entails, or scene impact. For a mutation tool without structured support, it should provide more context on outcomes and potential issues.

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 fully. It does so by explaining all three parameters: 'name' as the object name in scene, 'task_uuid' for MAIN_SITE mode from the generate model step, and 'request_id' for FAL_AI mode from the generate model step. It adds crucial semantics beyond the schema, clarifying the purpose and constraints of each parameter, especially the exclusive choice between task_uuid and request_id.

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 'import' and the resource 'asset generated by Hyper3D Rodin', specifying it's for assets after generation completion. It distinguishes from siblings like 'download_polyhaven_asset' or 'generate_hyper3d_model_via_text' by focusing on importing already-generated assets rather than creating or downloading external ones. However, it doesn't explicitly contrast with 'poll_rodin_job_status' which might relate to generation status.

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: after a Hyper3D Rodin generation task is completed, and it specifies two modes (MAIN_SITE and FAL_AI) with corresponding parameters. It includes an explicit instruction to 'Only give one of {task_uuid, request_id} based on the Hyper3D Rodin Mode!', which guides usage. However, it doesn't mention when NOT to use it or explicitly name alternatives among siblings, such as 'poll_rodin_job_status' for checking status before import.

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