superset_group_list

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

With no annotations, the description provides important behavioral details: pagination starting at page 0, a maximum page_size of 100, and automatic pagination for get_all. It also gives a concrete RISON filter example. The read-only nature is implied by 'List' but not stated explicitly.

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-line summary, brief domain context, and a clean parameter list. Every sentence adds value without redundancy.

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 output schema, the description covers the essential usage and parameter semantics. It does not explicitly mention authentication or read-only status, but for a list operation this is sufficient.

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 four parameters are explained with meaningful semantics beyond the schema, including a RISON filter example for q. Since schema coverage is 0%, this fully compensates for the lack of structured descriptions.

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 states 'List Superset user groups' with a specific verb and resource. It also explains that a group combines users and roles, which distinguishes this from related tools like superset_group_get or superset_group_create.

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 gives clear context for when to use this tool, including pagination options and the get_all flag for fetching all records. It does not explicitly name alternative endpoints, but the purpose and usage are unambiguous.

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