Create a 360-degree turntable image sequence by specifying a file path to store the exported images.
Export a 360-degree turntable image sequence.
Args: file_path: Absolute path (directory or base name) for turntable images.
| Name | Required | Description | Default |
|---|---|---|---|
| file_path | Yes |
Changes observed during successful MCP inspections.
v0.5.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose behavior, but it only states the action without mentioning side effects, file creation, overwrite behavior, or prerequisites. The agent cannot know what happens when it runs.
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 concise, front-loads the purpose, and includes a structured Args section. It is not bloated, but it lacks detail that could be added without losing conciseness.
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 lack of annotations and output schema, the description is too sparse to fully inform the agent. It omits details about the output format, file naming, required state, and potential side effects, making it insufficient for safe invocation.
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 description explains file_path as an absolute path that can be a directory or base name, adding meaning beyond the schema's type. However, it doesn't clarify how these two modes differ or what the tool does with the path, leaving 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 tool exports a 360-degree turntable image sequence, which is a specific export type distinct from siblings like export_obj or export_thumbnail. However, it doesn't specify what object the turntable is of, leaving some ambiguity.
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 on when to use this tool vs other export tools. The description doesn't mention alternatives or selection criteria, so an agent must infer usage from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.