superset_dataset_list

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

With no annotations, the description carries the full burden and does well: it discloses pagination behavior (lists across every page), that rows are "compact" (a field subset), the truncation flag, and the max_results cutoff at 500. It does not explicitly state read-only semantics, permission requirements, or rate limits, which are the remaining gaps for a 0-annotation definition.

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?

Front-loads the purpose sentence, then Args and Returns blocks with no filler. The Args block slightly restates parameter names that already exist in the schema, but each line adds semantic value, so waste is minimal.

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?

No output schema and no annotations, so the description must cover returns and safety; it describes the return payload (count, returned, truncated, rows) and per-row fields. What is missing is only auth/permission context, which is a minor omission for a list operation.

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 coverage is 0%, yet all four parameters are explained with meaning beyond the schema: search matches table name case-insensitively, database_id filters by database, mine scopes to the logged-in user, and max_results caps rows. This fully compensates for the absent schema descriptions.

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?

States a specific verb and resource ("List datasets") plus scope ("across every page of results, one compact row per dataset"). The phrase "Use superset_dataset_get_by_id for columns and metrics" explicitly differentiates it from the closest sibling reader, so an agent can route without opening either schema.

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?

Names the alternative (superset_dataset_get_by_id) and the condition that selects it (need columns/metrics rather than summary rows). However, it gives no guidance on when-not to use this tool versus other discovery tools like superset_database_get_tables or superset_chart_list, and no prerequisites or auth context.

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