Get a detailed description of any Scene Nodes asset by loading it into a temporary isolated Cinema 4D document, ensuring safe inspection without modifying your current project.
Describe a Scene Nodes asset in an isolated temporary document.
| Name | Required | Description | Default |
|---|---|---|---|
| asset_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the behavioral disclosure burden. The phrase 'isolated temporary document' usefully suggests a non-destructive, quarantined operation, but it does not clarify what happens to the document, whether the main scene is touched, or what side effects occur beyond the description.
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 a single, front-loaded sentence with no wasted words. It is concise, though slightly under-specified in content; the structure itself is clean and readable.
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?
For a one-parameter tool with an output schema, the description provides a minimally viable level of context: action, resource, and isolation. However, it omits where asset IDs come from, how this tool relates to asset search siblings, and any prerequisites for calling it.
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 only parameter, asset_id, has no schema description (0% coverage), and the tool description does not explain its meaning, format, or how to obtain it. The property name implies it is an ID, but the description adds no value beyond that.
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 a specific action ('Describe') and resource ('Scene Nodes asset'), and the added 'isolated temporary document' gives useful context. It is somewhat distinguishable from siblings like search_scene_node_assets, though it does not explicitly contrast with inspect_scene_nodes_graph or describe_capsule_asset.
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?
No guidance is given for when to use this tool instead of alternatives such as search_scene_node_assets or inspect_scene_nodes_graph. There are no conditions, exclusions, or recommended sibling tools mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.