Discover groups

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

Annotations already declare read-only, open-world, idempotent, and non-destructive behavior, so the description does not need to cover safety basics. It adds useful behavior beyond annotations: 30 results per page, passing next_cursor back as cursor, the fields returned, and the exclusion of private hidden groups.

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 front-loaded with the core purpose and then adds the most useful operational details: result fields, pagination, cursor reuse, and scope limitations. There is a small amount of repetition around 'public directory/list of communities,' but every sentence contributes useful information.

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?

There is no output schema, so the description appropriately lists the directory fields returned and explains pagination. Combined with annotations covering safety and open-world behavior, it gives an agent enough context to call 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?

Schema description coverage is 100%, and the schema already explains query and cursor semantics, including that an omitted query returns top groups. The description adds page size and cursor passback guidance, but this is only a modest supplement over the schema.

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 a specific verb and resource: searching Skool's public directory of communities. The emphasis on the public discovery directory, plus the note that hidden private groups are excluded, distinguishes it from sibling tools like list_groups and search_group that operate on known/private groups.

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?

It gives clear usage context: this is the public community discovery search, equivalent to skool.com/discovery's search box, and hidden private groups will not appear. It does not explicitly name sibling alternatives such as list_groups or search_group, so it stops short of fully explicit when-to-use-vs-alternative guidance.

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