superset_list_all_datasets

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

No annotations are provided, so the description carries the burden of disclosing behavior. It clearly states that all pages are fetched, which is a key behavioral trait of pagination. It does not mention rate limits or potential performance implications, but for a list operation, this is a reasonable disclosure.

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 two sentences long, front-loaded with the core purpose, and includes a brief, relevant usage example. Every word earns its place with no fluff.

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?

The tool is simple with one optional parameter and has an output schema. The description provides the core behavior and a usage context, making it easy for an agent to decide when to invoke it. The only gap is the unexplained page_size parameter, but this is a minor omission given the tool's simplicity.

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 schema has one optional parameter, page_size, with a default of 100, but the description makes no mention of it. With 0% schema description coverage, the description should compensate by explaining how page_size affects the results. It fails to do so, leaving the agent to infer from the name alone.

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 all datasets in Superset across all pages. It uses a specific verb ('List') and resource ('datasets'), and the phrase 'across all pages' differentiates it from the sibling tool superset_list_datasets, which likely does not paginate fully.

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 says 'Use when you need the full list' and provides a concrete example (finding a dataset by name like vw_bioverse_performance_report). It does not explicitly name the alternative sibling, but the usage context is clear.

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