superset_saved_query_list

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

The description discloses pagination semantics (page starts at 0, page_size max 100, get_all ignores page/page_size) and provides filter examples. However, with no annotations provided, it only implies read-only behavior via 'Retrieve' and does not mention authentication, ownership scope, or error conditions.

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 concise and well-organized, opening with a one-line purpose statement followed by clearly labeled argument bullet points. Examples are embedded directly without fluff, earning their place.

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?

Given the existence of an output schema (so return values need not be described), the description covers all parameters and their interactions (pagination vs get_all), provides filter syntax, and is sufficient for a list operation of moderate complexity.

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%, but the description fully compensates by explaining each parameter: page, page_size, q (with concrete RISON examples for label and database filters), and get_all (automatic pagination). This adds substantial meaning beyond the schema's bare types and defaults.

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 uses a specific verb ('Retrieve') and resource ('list of saved SQL queries'), clearly distinguishing it from siblings like superset_query_list (executed queries) and superset_saved_query_get (single query).

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?

No guidance is given on when to use this tool versus alternatives such as superset_saved_query_get or superset_query_list. The description focuses on parameters but does not provide context or exclusions for choosing this list endpoint.

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