bx24_smart_processes

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states that the tool supports CRUD operations, which implies mutation, but it does not warn about destructive actions like deletes, does not mention permissions or authentication needs, and provides no information about rate limits or side effects. The mention of REST 1.0 + 3.0 adds technical context but not behavioral 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 compact and front-loaded, immediately stating the tool's scope and operation families. The bilingual keyword list is useful for retrieval and does not introduce fluff or redundancy. Every part of the description earns its place.

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?

Given that the tool is complex (10 parameters, nested objects, 10 actions) and has no output schema or annotations, the description is adequate at a high level but not fully complete. It covers the core scope and action families, and the schema covers all parameters, but there is no guidance on expected responses, error behavior, or operational workflows such as needing confirm for deletes. The input schema fills some gaps, so this is a solid but not exceptional definition.

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 description adds meaningful semantics by explaining that type_* actions manage types while item_* actions manage items, and by noting that item operations require entityTypeId equal to the type id. It also provides bilingual aliases that help clarify the conceptual domain, which is valuable beyond the bare schema.

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 tool as handling Bitrix24 smart processes (произвольные CRM-сущности) with 'types + items CRUD' and explicitly names the method families crm.type.* and crm.item.*. This distinguishes it from the sibling CRM tools, which target standard entities like deals, leads, or contacts.

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 usage for custom CRM entities through phrases like 'smart process' and 'custom entity', which helps an agent choose this over standard CRM tools. However, it does not explicitly state when NOT to use it, nor does it provide alternative tool routing or conditions for choosing type_* vs item_* operations beyond what the schema already says.

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