search_leads

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

With no annotations provided, the description carries the full burden and does disclose two useful traits: results are paginated and a module prerequisite gates execution. It still omits read-only/safety framing and any mention of auth scope or limits, so it is good but not exhaustive.

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?

Three short sentences, front-loaded with the core purpose, then filters, then prerequisite and return behavior. Every clause adds information an agent needs and nothing is wasted.

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 six-parameter, all-optional search tool with no annotations and no output schema, the description covers purpose, filter surface, module prerequisite, and pagination. Remaining gaps (default page size behavior, whether an empty filter returns everything) are minor.

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 100%, so all six parameters are already documented with per-field meanings. The description only groups the filters (status, lead source, tag, text) without adding format, enum, or default details beyond the schema, matching the baseline for high-coverage schemas.

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 and resource ('Search CRM leads (prospective customers)') and immediately enumerates the filterable dimensions. The parenthetical distinguishes leads from the many sibling search tools like search_customers, search_deals, and search_accounts.

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?

Gives explicit preconditions: the Sales module is required and get_enabled_modules should be called first for self-service (CB) orgs, naming a concrete sibling tool. It does not, however, state when to prefer this over get_lead for a single record or search_deals for related entities.

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