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

The read-only, idempotent, non-destructive behavior is already disclosed by annotations, lowering the description's burden. The description does add that this covers the full directory and supports search/filtering, but it does not disclose pagination behavior, response scaling, or other execution nuances.

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 extremely efficient: two sentences, no filler, front-loaded action and followed by a 'when to use' sentence. Every sentence earns its place.

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 a 20-parameter schema with no per-parameter descriptions and no output schema, this description is too sparse to fully support correct invocation. It does not cover pagination, sorting, filter combinations, or the meaning of the many specialized filters, even though this is a complex list/search tool.

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?

With 0% schema description coverage, the description correctly maps the user intention to parameter categories like rating, tag, status, and free-text search. However, it leaves many parameters unexplained, including cursor, pageSize, sortBy, sortDir, region, leader, botFilter, insiderFilter, and the dimension filters.

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 explicitly names a concrete verb-resource pair ('Browse or search a project's full member directory') and gives a specific differentiating set of dimensions: rating, tag, status, and free-text search. This clearly distinguishes the tool from the engagement-rank-oriented sibling tools.

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 contains an explicit 'Use when...' clause and a negative hint: 'rather than by engagement rank.' However, it never names the sibling alternative(s), such as sm_list_leaders, so an agent is not fully routed to the correct alternative.

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