crm_search_leads

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

With no annotations provided, the description carries full burden but only states it searches with filters. It doesn't disclose behavioral traits such as whether it's read-only, pagination behavior (implied by 'limit' and 'after' parameters but not explained), rate limits, authentication needs, or what the output looks like. This leaves significant gaps for a search tool with complex parameters.

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 appropriately sized for a simple statement, though it could be more informative. The structure is straightforward but lacks depth.

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 objects in schema, no output schema, and no annotations), the description is incomplete. It doesn't explain parameter usage, output format, or behavioral context, making it inadequate for guiding an AI agent effectively with this tool's rich input schema.

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%, so the description must compensate but only mentions 'lead-specific filters' vaguely. It doesn't explain the meaning or usage of any parameters (filterGroups, properties, limit, after, sorts), leaving them undocumented. This fails to add value beyond the 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?

The description 'Search leads with lead-specific filters' states the verb ('search') and resource ('leads'), but it's vague about what 'lead-specific filters' means and doesn't distinguish this tool from sibling search tools like crm_search_companies or crm_search_contacts. It provides 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_search_objects or crm_get_lead. The description implies it's for searching leads, but there's no mention of prerequisites, limitations, or comparison to other search methods in the sibling list.

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