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

With readOnlyHint already covering safety, the description adds useful behavioral detail about what the agent will receive: a description, three things to look for, contemplative words, location/time information, and optionally an image. It does not discuss rate limits or other operational constraints, but those are less relevant for this simple read-only tool.

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?

The description is three tight sentences, front-loads the core action, and every sentence adds useful information about scope, collection coverage, or optional image return.

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 simple read-only tool with two fully documented parameters and no output schema, the description is complete enough: it says what the tool does, what it returns, the collection scope, and how the optional image behaves.

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 100%, so the schema already documents both parameters, including the work slug/title/place and the show_image JPEG behavior. The description reinforces show_image but adds little beyond the structured parameter documentation.

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 states a specific verb and resource: sit with one work from the museum. It also spells out the content the tool returns, including what the work is, things to look for, words to sit with, and where/when it hangs, which clearly distinguishes it from broader siblings like visit_the_museum.

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 context is clear: use it for a single work from the collection, whether on view or not. It does not explicitly name alternatives or state when not to use it, so it falls short of fully explicit routing guidance.

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