bx24_crm_calllists

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

No annotations are provided, so the description must disclose behavior itself. It only names operations and REST versions; it does not explain side effects, destructive outcomes, permission needs, or behavior of 'start' and 'status' beyond their names. The destructive nature of delete appears only in the schema, not the description.

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 compact and front-loaded with the core resource and operations. The RU/EN synonym list is useful for multilingual lookup and does not add meaningful bloat. It is appropriately sized for a multi-action tool though it lacks depth.

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?

Although the schema is rich and covers 100% of parameters, the description itself does not explain per-action required fields, expected responses, or operational details for a tool that multiplexes six distinct actions. With no output schema and no annotations, an agent is left without enough context to confidently invoke actions like add, start, or status.

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 100%, so the parameter descriptions already document id, order, start, action, fields, filter, select, and confirm. The tool description adds no parameter-level meaning, but the schema carries the burden, so the baseline of 3 is appropriate.

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 names a specific resource (Bitrix24 CRM call lists) and enumerates the concrete operations: create, list, get, delete, start, status. It also identifies the underlying REST method family crm.calllist.*, making it clearly distinguishable from sibling CRM tools.

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 lists operations but provides no guidance on when to choose this tool over alternatives such as bx24_call or bx24_telephony. It does not state prerequisites, exclusions, or scenarios where a different tool would be more appropriate.

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