discord_search_members

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

Annotations already declare readOnlyHint=true, so the trailing 'Read-only' is redundant and earns no credit. The useful additions are the prefix-only matching constraint (not mid-string or fuzzy) and the documented return shape ({ members: [...] } with id, username, nickname, roles). Nothing contradicts the annotations.

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 short sentences, front-loaded with purpose, then return shape, then the sibling routing hint. The final 'Read-only' fragment duplicates the annotation and is the one piece of dead weight.

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 three-parameter read, the description plus a full-coverage schema and an output schema covers what an agent needs. Minor gaps remain: case sensitivity of the prefix match and behavior on zero results are unstated.

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 coverage is 100% and the schema already states that query is a prefix matched against usernames and nicknames, and that limit is 1–100 with default 25. The description's prefix phrasing restates the schema rather than adding to it, so the baseline 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?

States a specific verb (Find), resource (server members), and precise matching semantics (prefix match on username or nickname), plus the return shape. This clearly separates it from discord_list_members without opening either schema.

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?

Explicitly names discord_list_members as the alternative and gives the condition that selects it ('to page through everyone'). It does not address why an agent would prefer this over discord_get_member_info when the target is already known, but the primary decision point is covered.

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