kommo_search_contact_by_phone

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

No annotations provided, so description carries full burden. It only states 'search' implying read-only, but lacks disclosure of return format, pagination, or limitations (e.g., exact match vs partial). Minimal behavioral context.

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?

Single sentence of 6 words is efficient, but could benefit from slight expansion for clarity. No wasted words, but structure is minimal.

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?

No output schema; description fails to clarify return behavior (e.g., returns matching contacts, multiple results). Given sibling search tools, more context is needed for completeness. Missing info on what happens with optional name parameter.

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 100%, but description adds no value beyond repeating 'phone number' and 'Optional: Name'. No explanation of phone format or how optional name is used (e.g., combined search). Baseline 3 reduced due to lack of added meaning.

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 for contacts by phone number' clearly states the verb (search), resource (contacts), and specific criterion (phone number), distinguishing it from siblings like 'kommo_search_contact_by_email' or 'kommo_list_contacts'.

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 vs alternatives like 'kommo_list_contacts' or 'kommo_search_contact_by_email'. No exclusions or context for optimal use.

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