Get Artwork Image

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses that not all artworks have images, returns metadata and viewer link (not bytes), and advises against constructing IIIF URLs manually. Annotations are all false (no special behavior), and description adds valuable context beyond them.

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?

Four sentences, front-loaded with purpose, then usage rules, then additional notes. No redundant or vague language.

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?

Given the tool has only one required parameter and an output schema exists, the description fully covers usage context, limitations, and differentiation from sibling tools.

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 100% with one parameter (objectNumber) already described. Description does not add new semantic information beyond restating 'object number' in context. 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?

Explicitly states it opens an interactive deep-zoom viewer for 'see/show/view' requests, and distinguishes from inspect_artwork_image which is for LLM visual analysis. Verb and resource are specific.

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 when-to-call (user wants to see, show, view) and when-not-to-call (list, summary, count, text-only). Names alternative tool inspect_artwork_image for visual analysis.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.