ads_discord_member_search

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

With no annotations, the description carries the burden. 'Search' implies a read-only operation and the note that finding a member doesn't authorize contacting them adds a useful compliance constraint, but it says nothing about permissions, rate limits, pagination, or what a match looks like.

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?

Two tight sentences, with the core action and scope front-loaded and the authorization caveat following. No wasted phrasing.

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 three-parameter search with no output schema and no annotations, the description covers the query semantics but omits the limit parameter, result shape, and permission requirements. Adequate but clearly incomplete.

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 0%, so the description must compensate. It clarifies that query matches username or nickname and that guild_id refers to one installed Discord server, but it never explains the 'limit' parameter or its 1-1000 range, leaving a real gap.

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 (search), resource (members), and scope (by username or nickname inside one installed Discord server). This distinguishes it from ads_discord_message_search and ads_discord_channel_list, though it doesn't explicitly name those siblings.

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 scoping constraint ('inside one installed Discord server') and the authorization caveat give implicit guidance on when and how to use it. However, there is no explicit when-to-use vs. alternatives (e.g., status/guild_list for discovery) and no exclusions beyond the contacting disclaimer.

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