Browse Set

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

Annotations already provide readOnlyHint=true and idempotentHint=true. Description adds performance info (DB-backed, tens of ms), resumptionToken portability limitations, and notes that includeExtentText is large. Does not cover error cases or rate limits, but adds meaningful behavioral context.

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 concise yet comprehensive, with clear structure: purpose, performance, return fields, linking to other tools, and pagination details. Every sentence adds value.

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?

Given the tool's complexity (4 parameters, output schema exists), the description covers all essential aspects: input, output fields, pagination, and connections to sibling tools. No gaps identified.

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?

Parameters have 100% schema coverage, so baseline is 3. The description adds value by explaining that setSpec comes from list_curated_sets, resumptionToken is stateless and not portable across upgrades, and includeExtentText defaults false and is large.

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 clearly states the tool enumerates member artworks of a curated set by setSpec, using a specific verb and resource. It distinguishes itself from sibling tools like list_curated_sets and get_artwork_details.

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?

Explicitly states to obtain setSpec from list_curated_sets, explains pagination via resumptionToken, and directs to use get_artwork_details for multi-row vocabularies. Clearly says 'Not for set discovery — use list_curated_sets first.'

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