discord_search_members

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

Annotations already include readOnlyHint=true, indicating no side effects. The description adds valuable behavioral context: the search is a prefix match, returns specific fields, and is read-only. This enriches the agent's understanding beyond what annotations provide.

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 composed of three concise sentences: the core functionality, the return structure, and a guidance to a sibling tool. Every sentence earns its place with no redundancy or extraneous information.

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, the description is mostly complete, covering purpose, parameters implicitly via schema, and output structure. However, it does not mention behaviors like case sensitivity, empty result handling, or rate limits, which could be useful for completeness.

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 has 100% coverage, so the baseline is 3. The description does not add significant new parameter details beyond what the schema already explains. The schema descriptions for each parameter are sufficient, and the tool description does not materially enhance them.

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 clearly states the tool's action ('Find server members'), specifies the resource ('members'), and details the matching criterion ('prefix match on username or nickname'). It effectively distinguishes itself from the sibling tool discord_list_members by highlighting the use case of prefix search versus paging.

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 explicitly advises to use discord_list_members for paging, providing clear guidance on when to use an alternative. However, it lacks explicit statements on when not to use this tool or other edge cases, such as case sensitivity or exact match scenarios.

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