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

Annotations already declare read-only, idempotent, non-destructive and non-open-world. The description adds genuinely useful context beyond them: it does not place an order or take payment, and no background work is started, which clarifies side-effect scope for an agent.

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?

Front-loaded with the core action and searchable facets, then boundaries. Slightly repetitive in the closing lines (read-only and no-background-work restate the same non-mutation idea), but no sentence is wasted.

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?

With no output schema, the description compensates by stating the return (a catalog id) and the nature of results (artwork pages, artist credits, sizes, finishes). Only the relationship to the sibling get_prints 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?

Schema coverage is 100% and there is a single optional parameter already documented with its facets and empty-means-whole-collection behavior. The description mentions the same facets, so it adds little beyond the schema; baseline 3 applies.

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 and resource (search the starting collection) plus the searchable facets (title, artist, subject). It never contrasts itself against the sibling get_prints, so an agent cannot tell from the description alone which of the two to pick.

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?

Implies when to use it by naming the searchable dimensions, and sets a boundary that prices/shipping need studio confirmation. However, there is no explicit when-not guidance or routing to the sibling get_prints, leaving selection to inference.

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