list_datasets

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

With no annotations, the description carries the full burden. "Currently loaded in memory" is genuine behavioral disclosure — it reveals that results are session state populated by load_dataset, not a catalog of all available data. It stops short of stating whether results are paginated or whether the list is empty when nothing is loaded.

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?

A single sentence with the scope qualifier front-loaded and no filler. Every word contributes to identifying the tool.

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 need no explanation, and with no parameters and no annotations there is little else required. The one omission is any pointer that the listing reflects prior load_dataset calls, though "loaded in memory" gestures at it.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. Nothing in the schema is left unexplained.

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?

Specific verb (List) plus resource (datasets) with a scoping qualifier ("currently loaded in memory") that distinguishes it from the other dataset tools. It does not, however, explicitly name a sibling or contrast itself with describe_dataset/query_dataset, which an agent might confuse for listing purposes.

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?

Usage is implied rather than stated: the name and the "loaded" qualifier make it fairly obvious this is a session-inventory call, but the description never says when to prefer it over describe_dataset or query_dataset, nor that it should follow load_dataset. For a zero-parameter tool this is a modest gap.

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