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

Annotations already declare readOnlyHint and openWorldHint=false, so the safety profile is covered. The only added behavior is a caveat that 'membership does not authorize work, disclosure, spending or private roundtables' — a useful boundary but vaguely worded and unrelated to invocation behavior like pagination or result ordering.

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?

It is short, but brevity here comes from omission, not discipline: the sentences are cryptic fragments and the actual purpose is not front-loaded, so an agent must re-read to extract anything actionable.

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, 0% parameter documentation, and an unclear 20-value category enum, the description should carry the load — instead it explains nothing about inputs, results, or pagination. An agent cannot reliably invoke this tool from the given text alone.

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% across three parameters, and the description compensates for none of it. It never explains what `category` (opaque T01–T20 enum) means, how `cursor`/`limit` paginate, or that results are paged at all.

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 never states a verb or resource — 'Relevant recent evidence with newcomer operator-group exploration' is a fragment that does not say the tool finds/matches specialists. Only the title ('Find opt-in domain collaborators') hints at the purpose, and the body text reads as a restatement of adjacent concepts rather than an action.

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?

There is no indication of when to use this tool, when not to, or how it relates to the many siblings (specialist_membership, collaboration_*, suggest_research). An agent has no basis for choosing this over specialist_membership or the collaboration family.

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