kommo_search_contacts

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

No annotations are provided, so the description bears the full burden. It only states that the tool searches contacts by text, failing to disclose read-only nature, permissions, rate limits, or behavior when no results are found. This is insufficient for an unannotated tool.

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 sentence with no extraneous words. It efficiently communicates the core purpose without repetition or filler.

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?

Despite low complexity, the description lacks essential context such as output format (list of contacts?), pagination behavior, and error handling. Without an output schema, agents are left to infer return structure, which hinders effective use.

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?

With 0% schema description coverage, the description partially clarifies the 'query' parameter (by naming search fields) but entirely omits 'page' and 'limit' parameters, which are common pagination controls but remain unexplained.

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 'Search contacts by text (name, phone, email)' using a specific verb and resource, and distinguishes from sibling tools like kommo_search_companies and kommo_search_leads which operate on different entities.

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 implies when to use (to search contacts by text) but provides no explicit guidance on when not to use it or alternatives. Given sibling tools for creating/updating contacts, the usage context is inferred but not elaborated.

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