superset_user_list

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

With no annotations provided, the description carries the full burden. It discloses pagination behavior, max page size, and the get_all flag, but does not explicitly state that this is a read-only operation or mention any authentication requirements or side effects. The examples for RISON filters add useful behavioral context, but deeper transparency is lacking.

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 clear lead sentence followed by a detailed args section. Each sentence provides necessary information, with no wasted words. The RISON examples are concise yet critical for usage.

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 tool's complexity (4 parameters, pagination, RISON filters), the description covers everything needed for correct invocation. The output schema exists, so return values need not be explained. The description is sufficient even without annotations.

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%, so the description fully compensates. It explains every parameter: page, page_size, q, and get_all, including max values and RISON examples. This gives the agent complete understanding of how to craft queries.

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 users' with a specific verb and resource. It distinguishes itself from sibling tools like superset_user_get by focusing on listing multiple users.

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 clear context for when to use the tool (listing users with optional filters), but does not explicitly mention alternatives or when not to use it. No exclusions are stated, but the pagination and filter examples imply typical usage.

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