Install any agent-installable Assetzaar product by slug. Free products return source or a short-lived signed download URL. Paid products require an agent key plus ownership; Pro products require an agent key plus active membership. For paid products, call purchase/check_purchase first.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | The product slug to install. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses return behavior for free products ('source or a short-lived signed download URL') and licensing requirements for paid/Pro products, but does not specify what the return value is for paid products or any side effects of installation.
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, two sentences long, and front-loaded with the core purpose. Every sentence provides useful information without 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 tool with one parameter, no annotations, and no output schema, the description covers the main aspects: what it does, variant behavior (free vs paid), prerequisites, and a required pre-call. It does not describe the output format for paid products, which is a minor gap but not critical for this simple tool.
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?
Schema description coverage is 100% for the single 'slug' parameter, so the schema already defines it. The description adds context about 'agent-installable' and the slug's role, but this is minimal beyond what the schema provides, hence the baseline score.
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 'Install any agent-installable Assetzaar product by slug' with a specific verb and resource, and it distinguishes itself from sibling tools like check_purchase, get_component, and purchase by focusing on installation.
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?
Provides explicit guidance: 'For paid products, call purchase/check_purchase first' and outlines the different requirements for free/paid/Pro products, giving clear direction on when and how to use the tool versus alternatives.
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.
Most tools have clearly distinct purposes, but there is some overlap: search and search_components both find products (one whole marketplace, one UI components only), and get_component and inspect both retrieve product information (one for source, one for manifest). These are distinguishable by their descriptions and use cases.
The tools follow a mostly consistent verb-based pattern with snake_case (check_purchase, get_component, search_components), but three tools are single verbs without an object (inspect, install, purchase). This is a minor deviation from the verb_noun convention used by the others.
Seven tools is well-scoped for a marketplace server. Each tool covers a necessary step in the workflow (search, evaluate, purchase, install) without bloat, and there are no redundant utilities.
The tool set covers the full marketplace lifecycle: discovery (search, search_components), evaluation (inspect, get_component), acquisition (purchase, check_purchase), and installation (install). The flow from search to install is seamless, with no obvious dead ends or missing critical operations.