search_clients_by_email

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

Description adds behavioral context: prefix match, 50-per-page limit, pagination with page parameter, and return of 0-50 clients. No annotations provided, so description carries full burden and covers key behaviors.

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?

Four sentences, well-structured, front-loaded with main purpose, then usage pattern. No wasted words.

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 all needed context: when to use, how to paginate, relation to siblings, return count. Has output schema so return details not needed in description.

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% (no descriptions in schema). Description compensates by explaining email is prefix match, page is for pagination with default 1. Adds meaning beyond bare schema.

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?

Clearly states 'Find clients by email address (prefix match, up to 50 per page)'. Specifies verb (find), resource (clients), and scope (email, prefix, limit). Distinguishes from sibling search_clients_by_phone.

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 says 'Use this before creating a lead to check whether the prospect already exists'. Provides common pattern: search, if found reuse client_id, else use portal_lead. Mentions pagination when count approaches 50.

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