crm_search_leads

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

No annotations are provided, so the description must fully disclose behavioral traits. It only mentions 'search' and 'filters,' failing to describe whether this is read-only, paginated, rate-limited, requires authentication, or returns structured data. For a search tool with 5 parameters and no annotations, this is a critical omission.

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 a single, efficient sentence with no wasted words. It's front-loaded and appropriately sized for the tool's name, though it could benefit from more detail given the complexity. The brevity is a strength but leads to under-specification.

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 complexity (5 parameters, nested filter structures, no output schema, and no annotations), the description is severely incomplete. It doesn't explain the search behavior, result format, error handling, or how to construct queries. For a tool with rich input schema but zero documentation, this is inadequate.

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%, meaning parameters like filterGroups, properties, limit, after, and sorts are undocumented in the schema. The description adds no semantic details about these parameters—it doesn't explain what filterGroups are, how to use properties for field selection, or what 'after' means for pagination. It fails to compensate for the schema 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?

The description 'Search leads with lead-specific filters' states the verb ('search') and resource ('leads'), but is vague about what constitutes 'lead-specific filters' and doesn't distinguish from sibling tools like crm_search_companies or crm_search_contacts. It provides a basic purpose but lacks specificity about scope or differentiation.

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?

No guidance is provided on when to use this tool versus alternatives like crm_get_lead (for single lead retrieval) or other search tools for different CRM objects. The description implies filtering but doesn't specify use cases, prerequisites, or exclusions, leaving the agent without contextual direction.

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