superset_dataset_list

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. It explains pagination behavior, that get_all fetches all records and ignores page/page_size, and that it returns a JSON string. It also provides RISON filter syntax examples, which adds useful behavioral context. It does not mention potential errors, rate limits, or authentication, but the core behaviors are well covered.

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 well-structured and concise, with an introduction, definition, important note, Args section with examples, and Returns line. Every sentence adds value, and the formatting makes it easy to scan. It avoids redundancy with the schema.

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 output schema exists, the description does not need to explain return structure, but it still covers key aspects: pagination, filtering, get_all mode, and its role relative to dataset_get. It is comprehensive for a list operation and provides enough context for an agent to select and invoke it correctly.

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 description has an explicit 'Args' section explaining each parameter in detail: page starts at 0, page_size max 100, q uses RISON with concrete examples, and get_all overrides pagination. This adds substantial meaning beyond the schema's basic type/default information and fully compensates for the 0% schema description coverage.

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 states the tool lists Superset datasets with pagination, defines what a dataset is, and explicitly distinguishes it from dataset_get by saying to call this first to discover current IDs. This is a specific verb+resource with clear sibling differentiation.

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 explicit usage guidance by stating 'IMPORTANT: always call before dataset_get to discover current IDs', giving a clear when-to-use context. It also includes detailed filtering examples for searching by name, schema, and database, which implies practical use cases. However, it does not explicitly mention when not to use this tool in favor of other alternatives beyond dataset_get.

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