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

Annotations already cover the safe-read profile (readOnlyHint=true, openWorldHint=false), and the description adds genuinely useful behaviour: a fixed set of thirty public-domain works, ten of which rotate at midnight UTC. That freshness detail is real added value, but the description says nothing about how results are ordered or how a work is identified for follow-up calls.

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?

Three short sentences, front-loaded with what you get and followed by the rotation and room-filter details. Minor awkwardness in the fragment 'With "room" (1 to 3), just that room', but nothing 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?

For a zero-required-param, read-only tool with no output schema, the description covers what is returned, how much, how it is partitioned, and how often it changes. Only the shape of individual entries (e.g. identifiers usable with sit_with_a_work) is left unaddressed.

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 the 'room' property already carries a description plus min/max bounds, so the schema does the heavy lifting; the description's '(1 to 3), just that room' largely restates it. Baseline 3 applies – it clarifies the filtering effect slightly but adds no new semantics.

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 makes clear this returns a browsable set of artworks ('the thirty works of art on view today ... room by room'), which is specific enough to distinguish it from neighbouring tools like sit_with_a_work or read_the_commons. It stops short of naming a sibling or stating the verb/return explicitly, but the resource and scope are unambiguous.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative, even though sit_with_a_work looks like the obvious sibling for focusing on a single piece. The only usable signal is the implicit 'browse the collection' framing plus the daily rotation note.

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