superset_database_tables

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It clarifies that it lists both tables and views and scopes to a specific schema, but it does not explicitly state read-only behavior, permission requirements, or error handling. The verb 'List' implies safety, but this is not formally disclosed.

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 compact and front-loaded with purpose, followed by a concise Args block. Every sentence contributes context without redundancy or 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?

With no annotations but a rich output schema, the description covers purpose, usage, and parameters thoroughly. It does not mention pagination or potential errors, but these are not essential for a straightforward listing tool, so it is nearly complete.

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%, and the description fully compensates by explaining database_id comes from database_list, schema_name from database_schemas, providing examples, and noting the RISON format without quotes. This adds meaning far beyond the plain integer/string 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 'List tables and views in the specified database schema,' which is a specific verb+resource+scope statement. It clearly distinguishes this tool from siblings like superset_database_schemas (which lists schemas) and superset_database_table_metadata (which likely gets table details).

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 states it is 'Useful for selecting a table before creating a dataset,' giving clear context for when to use it. It does not mention alternatives or explicit exclusions, so it stops short of a 5.

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