superset_role_list

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

With no annotations provided, the description carries the burden of behavioral disclosure. It explains that get_all fetches ALL records and ignores page/page_size, defines page as starting from 0, caps page_size at 100, and provides a RISON filter example. This goes beyond a simple 'list' statement, though it could still mention auth implications or return format (the latter is covered by an output schema).

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: a one-sentence purpose, a short list of standard roles, then a labeled 'Args' section covering each parameter. Every sentence contributes practical information, with no redundancy or filler.

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 list tool, this description is comprehensive: it states the purpose, helps identify typical roles, explains pagination and filtering, and clarifies the get_all behavior. An output schema exists to describe the return structure, so the description does not need to duplicate that.

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%, but the description fully compensates by explaining every parameter: page, page_size, q (with a concrete RISON example), and get_all (with its behavior). This adds meaningful semantics beyond the bare schema fields and their 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 clearly states 'Get the list of Superset roles' — a specific verb+resource combination. Listing standard roles (Admin, Alpha, Gamma, sql_lab, Public) adds useful context and implicitly distinguishes this list operation from sibling tools like superset_role_get, superset_role_update, and superset_role_delete.

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 provides solid usage context for parameters (pagination, max page_size, get_all behavior) and a filter example, but it does not explicitly mention alternatives or exclusions (e.g., 'for a single role, use superset_role_get'). The intended use is implied rather than explicitly contrasted with siblings.

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