list-sets

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only states the basic function. It does not reveal whether the operation is read-only, how results are paginated, authentication requirements, or any side effects. The agent is left to infer behavior from the name and minimal text.

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 a single sentence with no unnecessary words. It is front-loaded with the action and resource, making it easy to parse quickly.

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 simplicity (no parameters, output schema present), the description adequately explains the tool's purpose and scope. However, it could mention whether the list is exhaustive or paginated, or clarify the role of OAI-PMH, but overall it is sufficient for a basic list endpoint.

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?

There are no parameters (schema coverage 100%), so the description adds marginal value by clarifying that 'sets' refer to collections/departments and specifying the data source. For a zero-parameter tool, this is above the baseline of 4.

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 specifies the action ('lists'), the resource ('organizational sets'), and adds explanatory context ('collections/departments') and the source ('Städel Museum OAI-PMH interface'), which distinguishes it from sibling tools that deal with museum objects or a specific explorer.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., when searching for objects vs. listing sets), and does not mention any prerequisites or contextual scenarios.

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