bitrix_list_contacts

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It only says 'list contacts with search by name' and omits return shape, default ordering, limit behavior, assignedId filtering, and the fact that search actually matches name or comment rather than only name.

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, front-loaded sentence with no wasted words. It is appropriately short, though the brevity comes at the cost of useful detail.

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 list tool with four optional parameters and no output schema, this description is too incomplete. It does not explain what the function returns, how pagination works, how filtering behaves, or when to prefer this over sibling contact tools. Only the basic purpose is present.

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 50%; limit and order have no descriptions. The tool description adds no new parameter-level meaning and even narrows the search behavior to 'by name', while the schema says the search parameter matches 'name or comment'. This is unhelpful and slightly misleading.

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 states a clear action and resource: listing Bitrix24 CRM contacts, with search capability. This is enough to distinguish it from single-contact tools like bitrix_get_contact, though it does not explicitly differentiate it from the sibling bitrix_find_contact.

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 given about when to use this tool versus alternatives such as bitrix_find_contact, bitrix_get_contact, or bitrix_list_users. The agent must infer usage entirely from the tool name and the one-line description.

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