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

Annotations already declare it read-only, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds value by enumerating the facets returned (totals, collections, resolutions, price range, availability, measured coverage) - useful since there is no output schema - though it says nothing about payload size or pagination.

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 front-loaded sentence with no wasted words, and the scope enumeration is placed immediately after the framing phrase.

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 and no parameters, the description's enumeration of returned facets is what makes the tool callable with confidence. It is nearly complete; a one-clause pointer to the sibling tools for follow-up exploration would close the remaining gap.

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?

Zero parameters, so per the rubric the baseline is 4; there is nothing parameter-level for the description to compensate for.

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 resource (the whole catalogue) and enumerates its scope (totals, collections, resolutions, price range, availability, measurement coverage). It reads as a summary/aggregate tool, distinguishable from browse_collections and search_artworks, though it never names those siblings.

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: 'a high-level view' suggests an entry point before drilling into collections or search, but the description never states when to prefer this over browse_collections or search_artworks, nor any prerequisites.

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