search_leads

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

With no annotations, the description carries the burden but only states it is a full-text search, returns a JSON array, and has a default limit. It does not disclose rate limits, side effects, or error behavior, making it adequate but not comprehensive.

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 concise with a clear lead sentence, a brief parameter list, and an example. It is front-loaded and efficient, though the structure could be slightly more organized.

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?

Given the low schema coverage and presence of an output schema, the description does not explain return structure detail (e.g., fields, pagination) or error handling. It is somewhat complete for a simple search but leaves gaps.

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%, and the description adds basic meaning by explaining 'term' as the search term and 'limit' as maximum results with default 100. However, it lacks details on accepted formats or edge cases, providing minimal compensation.

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 'Full-text search leads by term' and specifies it searches across 'lead titles and related content,' distinguishing it from sibling search tools like search_deals and search_organizations.

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 provides an example and default limit but lacks explicit guidance on when to use this tool vs siblings like search_all or other entity-specific searches, and does not specify when not to use it.

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