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

Annotations already declare readOnly/idempotent/openWorld, so the safety profile is covered. The description adds genuinely useful behavior: the 10-artwork cap, that heavy history sections are opt-in, and that image URLs carry rights status. It does not discuss error behavior when an id is unknown or partial-failure handling.

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 sentences, front-loaded with the verb and scope, and the field enumeration is dense but useful for selection. The long mid-sentence field list is slightly heavy, 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 an output schema present, the description need not explain return values, and it covers scope, source, limits, and the opt-in mechanism. The main residual gap is behavioral detail on missing/invalid ids, which is minor for a read-only fetch.

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 ids, sections defaults, and include_related_media fully. The description restates the sections opt-in and the id provenance but adds no syntax or format detail beyond the schema, so the 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 (fetch) and resource (full Art Institute of Chicago artwork records), enumerates the returned fields, and explicitly differentiates itself from the search siblings by noting ids originate from artic_search_artworks/exhibitions/artists. An agent can distinguish it from the search tools without opening any schema.

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?

Clearly signals the prerequisite context by stating where ids come from (the three search tools), which tells the agent this is the follow-up expand step after a search. It does not, however, state when NOT to use it or contrast against artic_lookup_vocabulary.

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