list_datasets

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It does not mention that only non-deleted datasets are returned by default, nor does it address ordering, pagination, or potential rate limits. The schema describes the include_deleted parameter, but the description omits behavioral details that would help an agent understand the tool's operation.

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 three-word sentence that efficiently communicates the tool's purpose. Every word earns its place with no redundancy or filler.

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?

Although an output schema exists (reducing the need to explain return values), the description lacks information on pagination, sorting, or default behavior regarding soft-deleted datasets. For a simple list tool, this is minimally adequate but leaves important context for an agent, especially given the complexity of sibling tools.

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% (the single include_deleted parameter has a clear description). The tool description adds no additional parameter context beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 'List registered datasets' uses a specific verb ('List') and resource ('datasets'), clearly distinguishing it from sibling tools like get_dataset (singular retrieval), create_dataset, and delete_dataset. It immediately conveys the tool's core function.

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, nor does it mention limitations like pagination, sorting, or performance considerations. For a list operation, some implicit understanding exists, but explicit context is absent.

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