List datasets

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

Beyond the `readOnlyHint`/`idempotentHint` annotations, it discloses pagination behavior, dataset volume, and completeness relative to the search index. These are meaningful runtime traits not visible in structured metadata and add real value for an agent.

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 purpose, a single targeted comparison sentence, then a terse, complete Args list. No filler or redundant restatement of the title.

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 and annotations covering safety/idempotency, the description covers purpose, alternative routing, filter semantics, and pagination. Nothing needed to invoke it correctly is missing.

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?

The input schema has no property descriptions (0% coverage), and the description compensates with an Args block for all five parameters, including the source of `publisher_identifier` (`list_publishers`), examples for `access_rights`, and semantics for `page`/`page_size`. This is exactly what an agent needs to construct valid input.

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 action ('List registered datasets') plus an optional filter, and explicitly contrasts itself with `search_catalog`, so an agent can distinguish it from its siblings without opening schemas. The scope is clear and the comparison reinforces what this endpoint is for.

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 explicitly names the alternative (`search_catalog`) and gives the deciding factors: correct pagination, complete ~2000-dataset register, and coverage of records the search index misses. This tells an agent when to choose this endpoint over the search-based sibling.

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