bx24_crm_webform

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

With no annotations, the description carries the full burden of behavioral disclosure. The term 'CRUD' hints at mutations and deletion, but the description does not disclose destructive side effects, permissions, irreversibility, or other behavioral traits. It leaves important safety context to the action enum descriptions rather than the tool description.

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-loads the core resource and operation families. The RU/EN synonym list adds some redundancy but may help match user intent in different languages. Overall, it is concise without being underspecified at the topic level.

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?

Despite having a rich action enum and full schema coverage, the tool lacks an output schema and annotations. The description does not explain return values, pagination behavior, destructive-action confirmation, or the REST 1.0 vs 3.0 implications. For a tool with this many operation families, the description alone is not enough for confident invocation.

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 even though the tool description itself adds no parameter-level meaning. The inline action descriptions in the schema effectively document the 16 operations, so the agent has enough parameter context, but the top-level description contributes nothing extra.

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 as Bitrix24 CRM webforms plus their results and options, and names the API method families (crm.webform.*, crm.webform.result.*, crm.webform.option.*). It is specific enough to distinguish from sibling CRM entity tools, though it does not explicitly contrast itself with any sibling.

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 states what the tool covers but provides no guidance on when to choose it over alternatives, nor when not to use it. There is no mention of prerequisites, preferred use cases, or exclusions that would help an agent decide between this tool and the many sibling CRM tools.

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