KOINE collection overview: name, total supply, the artist agent DAEMON, contract address, chain, and links. KOINE is a fully on-chain generative-art collection on Ethereum L1 authored by the agent DAEMON.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It implies a read-only overview by listing informational fields and avoids any hint of mutation, but it does not explicitly state that there are no side effects or describe any access constraints. The behavior is adequately transparent for a zero-parameter info tool, though not deeply detailed.
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?
Two sentences, with the core overview scope and contents front-loaded in the first clause. Every phrase earns its place: the second sentence adds necessary context about the collection's on-chain nature and author 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 simple, zero-parameter tool with no output schema, the description is complete: it names the resource and lists the expected returned fields. The background about Ethereum L1 and DAEMON gives helpful context, and no critical invocation detail is missing.
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 has zero parameters, so the baseline is 4. The description adds no parameter-level detail because none is needed, and it appropriately focuses on what the returned overview contains.
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 resource scope, 'KOINE collection overview,' and enumerates the exact contents: name, total supply, DAEMON, contract address, chain, and links. This clearly distinguishes it from sibling tools like koine_get_piece or nonce_info, which target different resources or granularity.
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?
The phrase 'KOINE collection overview' signals that this tool is for high-level collection information, while the sibling set implies that piece-level queries belong elsewhere. It does not explicitly mention when not to use it, but the scope is clear enough for an agent to select it for overview-style requests.
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.
The koine_ and nonce_ prefixes cleanly separate two distinct collection workflows, and within each prefix every tool addresses a unique action or resource. Even the two verify tools are easily distinguished by collection prefix and their exact verification behavior.
Tool names share a clear collection-prefix snake_case scheme, making grouping and selection predictable. However, not every name follows the same verb_noun form—info, census, spec, listings, and provenance are noun-style while mine, get, list, and verify are verb-style—so the pattern is consistent but not perfectly uniform.
13 tools is well-scoped for a server covering two distinct on-chain art collections with read, discovery, verification, and minting workflows. Each tool maps to a real operation, with no obvious filler or redundant entries.
The NONCE half covers the full lifecycle well: spec, mine, mint_packet, verify, info, census, and get_piece. The KOINE half covers discovery, provenance, listings, and verification, but the only acquisition route is external Seaport fulfillment, with no KOINE purchase or fulfillment packet equivalent to nonce_mint_packet—a minor but real gap.