bx24_crm_products

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

No annotations are provided, so the description itself carries the behavioral disclosure burden. The top-level description only lists entity domains and REST versions; it does not state that operations range from reads to destructive deletes, that document conduct/cancel changes inventory state, or that confirmations may be required. Some destructive cues exist inside the action enum descriptions in the schema, but the tool description itself does not provide this transparency.

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 fairly dense list of trade-catalog entities and RU/EN keyword synonyms, followed by the method-family note. It front-loads the domain but reads more like a tag cloud than a concise behavioral summary; the keyword block, while useful for search, adds length without operational guidance.

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, multi-action tool with 24 parameters, over 100 possible actions, nested objects, and no output schema or annotations. The description identifies what domain it covers but does not explain the action-selection pattern, shared parameter behavior, return shapes, error conditions, or side-effect semantics. The schema helps, but the tool-level description is not complete enough for an agent to invoke it confidently across its many actions.

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 every parameter has some documentation, and the `action` enum includes unusually detailed per-operation descriptions, including destructive flags and required fields like 'NAME required' for product_add. The main description adds no extra parameter-level meaning beyond naming the domain, so the baseline score 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 clearly identifies the resource domain: 'Bitrix24 trade catalog' and enumerates the managed entity types (products, sections, prices, stores, offers, SKUs, etc.). It also names the API family, 'Methods catalog.*', which distinguishes it from CRM modules like leads, deals, and contacts, though it does not explicitly name a sibling alternative.

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 the tool: any trade-catalog operation involving the listed entities and catalog.* REST methods. However, it does not explicitly state when not to use it, how it relates to siblings, or prerequisites such as catalog setup or permissions.

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