bx24_crm_invoices

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the method families (crm.item.*, crm.status.*), the injected entityTypeId=31, and the REST versions, which gives useful operational context. It does not reveal side effects, permissions, reversibility, or what happens on destructive actions, though the schema's 'confirm' parameter partially covers destructive actions.

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 entity and capability summary. Each sentence provides distinct value: domain, operations, technical method mapping, and multilingual search terms. The RU/EN list adds a bit of redundancy but is short and useful for Bitrix24's user base.

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 complex 10-parameter, 10-action tool with no output schema, the description provides a good orientation but not full operational completeness. It covers the main operation categories and technical context, yet lacks examples, response/return behavior, error conditions, and explicit guidance on combining actions like fields and product-rows operations.

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 schema already explains all parameters. The description adds some higher-level context about underlying API methods and REST versions, but it does not meaningfully clarify individual parameter semantics beyond what the schema provides. 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 clearly identifies the resource (Bitrix24 CRM invoices / SMART_INVOICE) and the scope of operations: CRUD, stages, and product rows. It distinguishes the tool from other CRM siblings by naming the invoice entity and the underlying methods crm.item.*. However, it is a multi-action wrapper rather than a single specific verb, so it does not define one crisp operation.

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 this tool is for invoice-related operations, product rows, and stage handling, and it provides Russian/English terms that help route queries. It does not explicitly state when to prefer this tool over alternatives or when not to use it, so the guidance is mostly inferred from the tool name and entity type.

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