discord_search_members

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

The description adds behavioral context beyond the readOnlyHint annotation by specifying the prefix match behavior and the exact return format (JSON array with fields). It also declares 'Read-only,' reinforcing the annotation. The openWorldHint is not further explained, but the tool's behavior is sufficiently clear.

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 concise, consisting of two short sentences. The first sentence covers purpose and return format, the second provides usage guidance and confirms read-only. Every sentence adds value without any redundant or filler content.

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 the tool's simplicity (prefix search with limit) and the schema covering all parameters, the description covers the essential: purpose, return format, and an alternative tool. It does not mention error handling or pagination details beyond the limit parameter, but the tool's behavior is well-defined for its complexity.

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?

The input schema already provides full descriptions for all three parameters (100% coverage). The description does not add new semantic details beyond 'prefix match,' which is already implied by the schema's description for 'query.' No additional constraints or nuances are introduced.

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 states the tool finds server members whose username or nickname starts with a query string (prefix match), which is a specific verb-resource-context. It also mentions the return structure (JSON array of id, username, nickname, roles) and distinguishes itself from discord_list_members, a sibling tool for paging through all members.

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 clearly advises using discord_list_members when needing to page through all members, providing an explicit alternative. It implies the tool is for targeted prefix-based searches but does not exhaustively list conditions for use or non-use.

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