discord_search_members

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

With no annotations, the description carries the full burden. It does communicate the core behavior: it searches by username/nickname prefix and is presumably a read-only operation. However, it does not disclose edge behavior such as whether the search is case-insensitive, whether it returns only matching guild members, or how limit affects results, which would add useful grounding.

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 a single focused sentence with no filler or repetition. It front-loads the operation and the matching criterion, so a model scanning many tools can absorb the purpose instantly.

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?

The output schema exists, so return-value details are not required, and the tool is relatively simple with only one required parameter. However, the description is thin for a search tool with an optional target guild and a limit: the agent must infer how `guild_id` scopes the search and what happens when it is null. It is sufficient but not rich.

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 0%, so the description must compensate for parameter clarity. It explains that `query` is matched against username/nickname prefix, but says nothing about `limit` or `guild_id`, even though those heavily affect what the tool returns and whether it searches a specific server.

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 names a specific operation ('search members') and a precise matching criterion ('username/nickname prefix'), which clearly distinguishes it from siblings like discord_list_members, discord_get_member, and discord_get_member_permissions. An agent can identify what this tool does without opening the 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?

The description does not state when to prefer this tool over discord_list_members or discord_get_member, nor does it mention any alternatives or exclusions. The usage context is only implicit from the word 'search,' with no guidance about when the prefix query is the right approach.

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