Retrieve the complete version history of an asset to track changes, compare iterations, and audit the evolution of your pixel art.
Get the full version history of an asset.
| Name | Required | Description | Default |
|---|---|---|---|
| asset_id | Yes | Asset identifier |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It only restates the purpose and does not mention pagination, ordering, return format, or what fields each version entry contains. 'Get' implies read-only, but no further behavioral detail is given.
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?
One concise sentence with no filler. The action and resource are front-loaded, making the purpose immediately clear.
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?
With no output schema and no annotations, the description should explain what the returned version history contains. It does not, leaving an agent to guess about response structure, ordering, and pagination, which are material for a tool returning 'full' history.
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 input schema already describes asset_id as 'Asset identifier' with 100% schema description coverage. The tool description adds no additional parameter semantics, so the baseline of 3 is appropriate.
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?
States a specific verb 'Get' and resource 'full version history of an asset'. The scope is clear enough to distinguish it from related siblings like art.asset.current or art.asset.inspect_version, though it does not explicitly name those alternatives.
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 on when to use this tool versus alternatives such as art.asset.current, art.asset.inspect_version, or art.asset.provenance. The only usage signal is the phrase 'full version history', which is implied rather than explicitly stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.