Get one work by slug: description, dimensions, materials/techniques, images, museum holder, exhibitions it appeared in, price when for sale, and graph relations.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and openWorldHint, so the description adds value by listing returned fields, but does not disclose additional behavioral traits beyond what annotations provide.
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?
A single, well-structured sentence that front-loads the action and key constraint, with no wasted words.
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 one parameter and no output schema, the description covers the return fields adequately, though it could optionally mention slug format constraints.
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 coverage is 0%, but the description explains the slug parameter's purpose ('by slug'), compensating for the lack of schema documentation.
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 it retrieves one work by slug and enumerates the returned fields (description, dimensions, images, etc.), distinguishing it from sibling tools like search_works (list) and get_artist (different entity).
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 description implies usage when you have a slug, but does not explicitly state when to use alternatives like search_works (when slug is unknown) or provide exclusions.
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 unique entity or action (e.g., get_artist vs. search_artists, get_relations vs. get_stats). No two tools have overlapping purposes, so an agent can clearly distinguish them.
All tools follow a consistent verb_noun pattern: either get_<entity> or search_<entity>. No mixing of conventions like camelCase or different verbs.
12 tools is well-scoped for an archive server covering artists, exhibitions, works, organizations, marks, press, and graph relations. Each tool earns its place without redundancy.
The tool surface covers the main entities (artists, works, exhibitions, organizations) and provides search and retrieval for all key types. Additional tools like get_relations and get_timeline fill gaps for connected data and chronology, making the set feel complete for its domain.