bx24_crm_deals

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

No annotations are present, so the description carries the full burden. It only labels operations as 'CRUD' and lists feature areas; it does not disclose that many bundled actions (delete, setProductRows, contact_items_delete, category_delete, etc.) are destructive or that some actions overwrite data. The agent cannot predict side effects or confirmation requirements from the description alone.

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?

Two dense sentences with the resource front-loaded and the capability list kept compact. The RU/EN trigger list is useful for matching user intent rather than filler, though the long comma-separated lists make it slightly less scannable than it could be.

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 35-action, 18-parameter tool with no annotations and no output schema, this is a minimal-but-adequate orientation: it names the domain, method families, and sample intents while leaving action semantics to the detailed schema. Gaps remain around destructive behavior, output shape, and the relationship between categories and stages, but the rich schema compensates substantially.

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?

All 18 parameters have schema descriptions (100% coverage), so the description is not required to repeat them. It adds high-level domain context (product rows, contact bindings) and multilingual task vocabulary, but no parameter-level detail beyond what the schema already provides.

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 the specific resource ('Bitrix24 CRM deals') and enumerates capability areas: CRUD, funnels/categories, product rows, contact bindings, timeline. The method-family list and multilingual task phrases make it easy to distinguish from siblings like bx24_crm_contacts or bx24_crm_products.

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 trigger phrases ('create deal, find deals, move stage, close deal, product rows') imply common use cases, but there is no explicit when-to-use vs alternatives or when-not-to-use guidance. An agent must infer deal-related usage from the name and domain list rather than being told when this tool beats a sibling.

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