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

No annotations are provided, so the description carries the full burden. It discloses that results include public groups and organization-visibility groups accessible to the caller, which is a meaningful behavioral detail about the data scope. However, it does not explicitly note that the operation is read-only or discuss other behavioral aspects, though that is largely implicit for a list operation.

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 compact and well-structured: a one-line purpose followed by a short bulleted 'Use when' section. Every sentence adds value, and the key purpose is front-loaded. There is no redundancy or fluff.

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 that an output schema exists, parameters are fully documented in the schema, and the description provides clear usage context and downstream integration hints (slug for submit_query), the definition is complete. An agent has everything it needs to select and invoke the tool correctly.

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?

The input schema covers all three parameters (page, api_key, page_size) with descriptions, so schema coverage is 100%. The description adds no additional meaning about these parameters; it only references the slug which is an output, not an input. Thus the baseline 3 applies.

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 ('List') and resource ('source groups') with a clarifying parenthetical ('named domain allowlists') that precisely identifies what the tool does. This clearly distinguishes it from other list_* siblings without ambiguity.

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 includes an explicit 'Use when' section with two concrete scenarios: discovering reusable domain sets and obtaining a slug for submit_query. It provides clear context for when to use the tool, though it does not explicitly state when not to use it or name a sibling alternative.

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