Browse Set

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description adds value through latency expectations ('warm calls in tens of ms'), pagination token semantics (stateless base64, not portable across server upgrades), and the record field list. It stops short of discussing error behavior or auth, so it is strong but not exhaustive.

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, then routing, return shape, and the exclusion last. Four dense sentences with little waste, though the return-field enumeration is somewhat long given an output schema exists.

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?

An output schema exists, so return values needn't be spelled out, yet the description still summarizes fields and gives pagination behavior and follow-up routing. Complete enough for an agent to call correctly; minor gaps are only around failure modes.

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%, so the schema already documents all four parameters and baseline would be 3. The description still adds meaning beyond the schema: setSpec provenance from list_curated_sets, the resumptionToken statelessness/upgrade caveat, and the note that includeExtentText is large and not rendered in the text channel.

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 (Enumerate) and resource (member artworks of one curated set) scoped by setSpec. It explicitly names the sibling tools it is not (list_curated_sets for discovery, get_artwork_details for details), so an agent can distinguish it without opening schemas.

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?

Provides explicit routing: get setSpec from list_curated_sets, follow up with get_artwork_details for multi-row vocab, and 'Not for set discovery — use list_curated_sets first.' Both when-to-use and when-not-to-use are covered with named alternatives.

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