superset_sqllab_execute

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

With no annotations, the description carries full disclosure burden. It reveals the 1000-row limit, default schema behavior, catalog optionality, and template_params usage. However, it does not explicitly warn that arbitrary SQL can include destructive operations or that permissions may be required. The 'IMPORTANT' caution is a general warning but lacks specificity about side effects.

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 with a front-loaded purpose, a cautionary note, metadata tool pointer, row limit, and a parameter list. Every section adds value and the length is justified by the need to document six parameters thoroughly.

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 presence of an output schema means return values need not be documented. The description covers prerequisites, limitations, and all parameters with examples. It does not mention error handling or asynchronous execution, but overall it is sufficient for correct invocation.

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?

All six parameters are explained in detail with examples for sql and template_params, default behavior for schema, and provenance for database_id. This fully compensates for the 0% schema_description_coverage and significantly adds meaning beyond the raw 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 clearly states it executes a SQL query via SQL Lab and returns the result, distinguishing it from siblings like superset_sqllab_export_csv (which exports) and superset_sqllab_format_sql (which formats). The action and output are explicit.

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?

It provides clear context for use (executing validated SQL queries) and references superset_database_table_metadata and superset_database_tables as prerequisite tools for schema discovery. It also notes the 1000-row limit, but does not explicitly state when to prefer alternative execution tools or exclude this tool for certain query types.

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