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 does disclose meaningful behavioral traits: results are pseudonymous, members appear as handles only, and no PII is returned. It omits result limits, pagination, and any auth requirements, so coverage is partial.

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?

Three tight clauses with the topic-vs-person distinction front-loaded, so the key routing signal comes first. The '[KEEP · internal]' prefix is editorial clutter that adds no value to an agent and slightly dilutes the opening.

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?

With no output schema and no annotations, the description should ideally sketch the return shape; it does give one hint (members are handles only) but says nothing about pagination, result caps, or ordering. For a discovery/list tool that is adequate but incomplete.

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 0% for the single q parameter, so the description must compensate. It partially does by saying q filters over topic/title/description, but gives no matching semantics (substring vs. fuzzy), no syntax, and no empty/missing behavior.

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?

States a specific verb (Discover/list) and resource (pseudonymous shared-study groups) plus the scoping dimension (by TOPIC, not by person). This clearly separates it from group_get, group_create, and group_join. The only weakness is the bracketed '[KEEP · internal]' tag, which is operational metadata rather than purpose.

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 parenthetical '(not by person)' implicitly tells the agent this is the topic-based discovery path, which is useful routing guidance. However, it never names a concrete alternative tool or states when not to use it, so the guidance remains implied rather than explicit.

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