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

No annotations are provided, so the description carries the burden. It discloses privacy-relevant behavior: groups are pseudonymous, members are handles only, no PII. This is useful context beyond 'list groups.' However, it does not state whether the operation is read-only, whether q is required for filtering or returns all groups when omitted, or any pagination/response format details.

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?

Two sentences, each earning their place. The first states the core purpose and scope, the second adds filtering and privacy details. No fluff or repetition.

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 simple tool with one optional parameter and no output schema, the description covers the key behaviors: topic-based discovery, optional filtering, pseudonymity, and absence of PII. It could mention what the response contains (e.g., list of group summaries), but the tool name implies 'list' and the description is adequate for the complexity level.

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 has only one parameter 'q' with zero description coverage. The description compensates by explaining that 'q' filters over 'topic/title/description' and is optional, which is essential semantic information not present in 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 clearly states a specific action ('Discover') on a specific resource ('pseudonymous shared-study groups') with a clear scope ('by TOPIC, not by person'). This distinguishes it from siblings like group_get (retrieving a specific group) and group_create (creating a group).

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 phrase 'by TOPIC (not by person)' provides clear guidance on when to use this tool: for topic-based discovery, not people-based lookup. It also explains the optional q filter's role. However, it does not explicitly mention alternatives like group_get or search, though the contrast is implied.

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