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

Annotations already declare readOnly, idempotent, non-destructive, openWorld behavior, so the bar is lower. The description adds genuine return-context: render plus indexed public owner with timestamp, and explicitly bounds scope by saying transfer history is excluded. It stops short of describing freshness/staleness of the indexed owner or failure behavior.

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 tight sentences with the primary action front-loaded and the scope limitation trailing. Nothing is padded, though 'through the existing artwork API' is internal implementation detail that occupies space an agent cannot act on.

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?

An output schema exists, so return values need not be re-explained, and the description does add the useful negative scope. However, for a two-parameter lookup with zero schema descriptions, it omits what slug/edition resolve to and what happens when no minted edition matches.

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 0%, so the description carries the burden for both required parameters, yet it never explains what 'slug' identifies (project, artist, or artwork) or what 'edition' indexes. 'Minted edition' hints at the edition parameter's meaning but leaves slug and the not-minted/error case unaddressed.

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?

States a specific verb (look up) and resource (a minted edition) and scopes it with 'through the existing artwork API.' The parenthetical 'not full transfer history' sharpens what the lookup covers, though it never names or contrasts a sibling such as prepare_artwork_display or get_collection_holdings.

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?

Usage is only implied by 'look up a minted edition.' There is no statement of when to reach for this versus the ~20 sibling tools, no prerequisites, and no exclusions beyond the transfer-history caveat.

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