search_members

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

Discloses authentication via API key, rate limits (max 10 concurrent requests), read-only nature, safe retry, and return format including exact matches first. No annotations provided, so description covers all needed behavioral info.

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?

Well-structured with paragraphs, args, returns, and example. Slightly verbose but each part adds value (alternative hints, behavioral notes, parameter details). Could shorten some phrases.

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?

Covers query rules, optional filtering, return structure with fields and ordering, and provides a concrete example. Output schema exists, so return format is further detailed. No major gaps identified.

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?

Adds significant meaning: query must be at least 3 characters, full email for exact match, partial for fuzzy; list_id optional to restrict to single audience. Schema coverage is 0%, so description fully compensates.

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 it searches for members across all audiences by email or name, returning exact and fuzzy matches. It uses a specific verb+resource and distinguishes itself from sibling tools like list_audience_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?

Explicitly tells when to use (looking for a specific person across audiences) and when not to (use list_audience_members for browsing a known audience), and suggests follow-up tools (get_member_activity, get_member_tags).

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