bx24_lists

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses only REST 1.0 + 3.0 support and domain terminology; it does not mention destructive operations (four of the twenty actions delete data), side effects, authentication needs, or pagination/limit behavior. The destructive flags and the confirm mechanism appear only in the schema's action enum, not in the description — so the description itself fails to convey the tool's safety profile.

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 — two substantive sentences plus a bilingual glossary — with the domain and method families front-loaded. The 'REST 1.0 + 3.0' note is valuable context, and the RU/EN term mapping earns its place given Bitrix24's bilingual user base. It loses one point because the glossary line is slightly redundant with the first sentence and could be tightened, but overall there is no wasted prose.

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?

This is a high-complexity tool — 14 parameters, 20 actions, nested objects, no output schema, and no annotations — yet the description only names the domain and REST versions. The rich action enum in the schema compensates substantially, but the description leaves unaddressed: what the operations return, how lists relate to fields/elements/sections, and any practical call patterns. It is minimally viable for an agent to select the tool, thanks largely to the schema, but not complete on its own.

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 baseline is 3; the schema already documents all 14 parameters, including per-action semantics in the action enum and the purpose of confirm, filter, order, and select. The description itself adds no parameter-level meaning — it only names resource families. It neither compensates for gaps (there are none) nor elevates understanding beyond the schema, so the baseline 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 identifies the resource domain precisely: Bitrix24 universal lists (infoblocks) with their sub-entities — lists, fields, elements, sections — and names the method families (lists.*, lists.element.*, lists.field.*, lists.section.*). This clearly distinguishes it from the CRM-entity siblings (bx24_crm_leads, bx24_crm_deals, etc.). It stops short of a 5 because it enumerates resources rather than stating a crisp verb+resource action, and the RU/EN glossary, while helpful, is not a purpose statement.

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?

Usage context is implied by the domain wording: an agent facing a request about Bitrix24 lists/infoblocks should select this tool, while CRM-entity requests route to the bx24_crm_* siblings. However, there is no explicit when-to-use guidance, no named alternatives, and no exclusions such as 'for CRM entities use bx24_crm_* instead.' The guidance is adequate but left entirely to inference.

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