crm_search_leads

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

No annotations are provided, so the description carries the full burden. It says 'Search' implying read-only, but does not state that explicitly, nor does it mention pagination, ordering, return format, or how results are limited. For a search tool, this is a significant gap.

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 concise sentence with no extraneous information. It is front-loaded with the verb and resource. However, it's so brief that it omits useful details, but that's a completeness issue, not a conciseness issue.

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 simple search tool with only two parameters and no output schema, the description should at least mention what is returned and how limit behaves. It also doesn't mention any result ordering or relevance. Given the simplicity, this is a moderate gap, making it minimally viable.

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%, so the description must compensate. It clarifies that the 'query' parameter searches by name, email, or company, which adds meaning beyond the schema. However, it does not explain the 'limit' parameter or its default/maximum, leaving it undocumented in both schema and description.

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?

Description states a clear verb 'Search' with resource 'CRM leads' and specifies searchable fields (name, email, company). This differentiates it from create operations like crm_create_lead and from hub_search_prospects, though it doesn't explicitly name any sibling as alternative. The purpose is unambiguous.

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 on when to use this tool versus alternatives like hub_search_prospects or search_fb_ads. It doesn't mention any prerequisite or scenario where this is preferred. The agent is left to infer from the name alone.

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