superset_database_list

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It clearly describes the listing behavior, return fields, pagination, and get_all behavior, as well as the IMPORTANT note about calling before database_get. It does not explicitly state that the operation is read-only, but 'list' implies it, and no contradictions exist.

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 a clear purpose, followed by return fields, an important usage note, and a structured Args section. Every sentence contributes value, and the parameter details are necessary given the schema's lack of descriptions. It is well-organized and not verbose.

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 description fully covers the tool's behavior, parameter semantics, and usage context. It explains return values despite having an output schema, provides examples for filters, covers pagination semantics, and includes the crucial sequencing directive with database_get. The output schema covers return details, so the description is complete for this simple list 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 input schema provides zero description coverage for parameters, so the description must fully compensate. The 'Args' section explains every parameter (page, page_size, q, get_all), includes RISON filter examples, mentions the page size max, and clarifies that get_all ignores page/page_size. This far exceeds the bare 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 opens with a specific verb and resource: 'List database connections configured in Superset.' It also states the return fields (ID, name, engine type, status), and explicitly distinguishes itself from the sibling tool database_get by instructing the agent to call this tool first to discover current IDs.

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 states when to use this tool: 'IMPORTANT: always call before database_get to discover current IDs.' It also provides parameter-level usage guidance for pagination and get_all, and explains the q filter with examples. This directly addresses when to use this tool vs the listed alternative.

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