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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds that matching is by name similar to an autocomplete mention box, which hints that results are a partial-match shortlist, but it says nothing about pagination or the 30-result ceiling enforced by the limit parameter.

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?

A single front-loaded sentence with no filler, conveying verb, resource, and matching mode. It is arguably too terse for a multi-parameter tool, but not padded.

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, annotated read tool this covers the essentials, but with no output schema the description does not indicate what a result entry looks like (name, handle, id) or that results are capped. A note that it returns member identifiers usable with get_member or invite_members would close the gap.

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%, so group, query, and limit are all documented in the schema already. The description's 'by name' adds only marginal semantics beyond the schema's 'Part of a name or handle,' so the baseline of 3 applies.

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?

Names a specific verb and resource ('find members of a group by name'), which clearly separates it from mutation siblings like ban_member or remove_member. It does not explicitly contrast with list_members or get_member, so the search-vs-enumerate distinction is left to inference.

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 '@mention box' analogy implies quick partial-name lookup for picking a member, which is useful implied guidance. However, there is no explicit statement of when to use this over list_members or get_member, nor any note about result caps.

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