list_datasets

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

No annotations are provided, so the description carries the transparency burden. It clearly conveys a read-only, non-destructive operation through 'List' and 'Free to browse.' It does not discuss rate limits or authentication, but for a zero-parameter catalog listing, it adequately signals the behavioral outcome.

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 front-loaded with the core action and output ('List all available datasets with record counts'), then adds a concise, useful list of dataset categories. Every clause earns its place—there is no filler or repetition of the tool name.

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?

For a zero-parameter, read-only discovery tool with no output schema, the description covers the essential contract: list datasets, show record counts, and browse for free. It doesn't specify output formatting or explicitly route to siblings, but this is complete enough for a simple catalog listing tool.

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 has 0 parameters, so the description has no parameter details to add. The baseline for 0-param tools is 4. The phrase 'List all available datasets' confirms there are no filters or inputs needed, which aligns with the empty input schema.

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 states a specific verb and resource: 'List all available datasets with record counts.' This clearly distinguishes it from siblings like list_products (different resource), fetch_dataset (fetches a single dataset), and purchase_data (transactional). The added dataset-category examples reinforce the scope of the resource.

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?

There is no explicit statement of when to use this tool versus alternatives. 'Free to browse' hints that this is a discovery/browsing endpoint before purchasing, but it does not say 'use fetch_dataset to get actual data' or 'use purchase_data to buy access.' Usage guidance is implied but not explicit.

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