superset_query_list

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

With no annotations present, the description carries the full burden and does disclose meaningful traits: newest-first ordering and, importantly, that history can be enormous and only the newest max_results are returned. It stops short of stating auth requirements or whether the operation is strictly read-only, but the truncation behavior is a valuable non-obvious 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?

Front-loaded with the one-line purpose, then a focused note on truncation, then Args/Returns. The Args section partly restates the schema, but the Returns section earns its place since there is no output schema. Efficient overall.

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?

For a simple single-parameter list tool with no annotations and no output schema, the description covers purpose, ordering, truncation, the parameter's meaning and default, and the return shape (count/returned/truncated/rows). Nothing essential is missing.

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 description coverage is 0%, so the description must compensate, and it does: 'max_results: Stop after this many rows (default 50)' explains both the cap semantics and the default for the only parameter. Minor residual ambiguity (whether it counts total rows or returns only a slice) is mitigated by the Returns section.

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 ('List') and resource ('SQL Lab query history') plus ordering ('most recent first'), so the agent knows exactly what it returns. However, it never distinguishes itself from near-neighbors like superset_sqllab_get_saved_queries or superset_query_get_by_id, leaving sibling disambiguation to inference.

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?

There is no when-to-use, when-not-to-use, or alternative guidance. The agent must infer that this is for browsing history versus fetching a single query by id or retrieving saved queries; nothing in the text routes it.

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