Search leads

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe read-only nature is covered. The description adds the behavioral nuance of 'full-text search' and 'by name/query', but does not explain pagination, result ordering, or the meaning of the 'with' parameter. No contradiction with annotations.

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 two concise sentences: the first states the purpose and the second provides an alternative. Every word earns its place, with no redundancy.

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 read-only and open-world annotations, the description is mostly adequate, but it does not explain the 'with' parameter or mention limit semantics or result expectations. The sibling distinction helps, but some parameters remain ambiguous.

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 only 33% (only query has a description 'Search text'). The description confirms query searches by name/query but leaves 'with' and 'limit' unexplained. Since coverage is low, the description should have compensated more for these undocumented parameters.

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 the tool performs full-text search for leads by name/query, using a specific verb and resource. It also explicitly distinguishes itself from the sibling tool kommo_leads_list by saying 'Prefer kommo_leads_list for advanced filters.'

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?

It gives direct usage guidance: use this for convenient full-text search, and use kommo_leads_list for advanced filters. This provides a clear when-to-use and when-not-to-use comparison with an alternative sibling tool.

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