Place your design onto product mockups (t-shirt, poster, canvas, phone case, mug, tote bag). Instant product visualization for e-commerce and print-on-demand. FREE. ($0.10 / 1 GCX)
| Name | Required | Description | Default |
|---|---|---|---|
| image | Yes | Base64-encoded design image | |
| product | No | Product type | tshirt |
| background_color | No | Background hex color | #f5f5f5 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, indicating safe, read-only behavior. The description adds pricing details ('FREE. ($0.10 / 1 GCX)') but no other behavioral traits beyond those implied by the annotations.
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?
Description is a single clear sentence followed by a brief cost note. All information is front-loaded and every word adds value with no redundancy.
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 simple tool with 3 parameters, no output schema, and clear annotations, the description sufficiently explains the tool's purpose, products, and cost. No gaps are evident for correct 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?
Input schema covers all 3 parameters with descriptions (e.g., 'Base64-encoded design image', 'Product type', 'Background hex color'). The description adds no additional semantic meaning beyond the schema, so baseline 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?
Description uses a specific verb ('Place your design onto product mockups') and resource ('product mockups'), listing all product types. It clearly distinguishes from sibling tools like remove_background or resize_image, which serve different purposes.
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?
Description states the use case ('e-commerce and print-on-demand') and that it's free, providing clear context. However, it does not specify when not to use this tool or mention alternatives, though siblings offer no direct substitute.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct operation—artwork retrieval, image processing, asset management, watermarking, etc.—with clear descriptions that prevent confusion. Even similar tools like enrich_metadata and get_artwork_oracle are differentiated by depth and purpose.
Tool names follow a consistent verb_noun pattern in snake_case (e.g., get_artwork, remove_background, register_hash). The few non-verb-starting names (compliance_manifest) are standard and do not break the overall pattern.
27 tools is slightly above the typical range but justifiable given the broad domain covering artwork access, image processing, and digital rights. Each tool serves a unique purpose without redundancy.
The tool set covers the full lifecycle: search, retrieve, analyze, edit, save, and verify assets. Gaps are minimal—e.g., no metadata deletion tool—but the core workflows are fully supported, and the inclusion of compliance and provenance tools adds value.