Apply a complete detail pass to an existing canvas session, using selected materials and profile settings to enrich previously drawn pixel art.
Run the full detail pass pipeline on an existing canvas session. Requires content already drawn on canvas.
| Name | Required | Description | Default |
|---|---|---|---|
| seed | No | Random seed | |
| profile | No | Detail profile level | medium |
| materials | Yes | Material types to apply | |
| session_id | Yes | Canvas session ID |
Changes observed during successful MCP inspections.
v0.3.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 explains what is run, not what happens to the canvas, whether the operation mutates or is destructive, whether it completes synchronously, or what result is produced.
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 one focused sentence that leads with the verb and resource, then adds a useful prerequisite. It is compact and contains no filler, though it would be more helpful with a bit more operational context.
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 4-parameter pipeline tool with no output schema and no annotations, the description is under-specified. The prerequisite is useful, but the behavior, side effects, and return/result of the pipeline are completely omitted.
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 documents all four parameters with 100% coverage, including the means for seed, profile, materials, and session_id. The description adds no deeper parameter meaning, so the baseline score 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?
The description uses a specific verb and resource (run, full detail pass pipeline) and a clear target (existing canvas session), so an agent understands what the scope is. It stops short of 5 because it does not explicitly differentiate from closely related art.detail.* tools such as plan or pass.
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?
It states the key prerequisite: content must already be drawn on canvas. This gives useful placement in a workflow, but there is no guidance about when to prefer this tool over art.detail.plan, art.detail.pass, or the individual detail pass variants.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.