b24_batch

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

With no annotations, the description carries the behavioral transparency burden. It does disclose the key behavior of executing multiple calls in one request and chaining outputs, which adds real value. However, it omits important behavioral details such as error handling, partial failures, batch limits, and the read-only vs write-webhook distinction.

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 concise sentences front-load the core purpose and the key chaining behavior. There is no fluff, and every word 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?

For a generic batch tool with no annotations and no output schema, the description is too sparse. It does not explain how to select or use the optional webhook parameters, whether writes require a specific webhook, what failure semantics look like, or how responses map to aliases beyond the $result hint. An agent would need to inspect the schema carefully and still lack operational context.

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?

The schema already documents the 'calls' parameter thoroughly with an example and the $result chaining syntax, so the description mostly restates what the schema provides. It adds no meaning for 'webhook_url' or how to choose between webhook_url and personal_webhook. With 67% schema coverage, this is adequate but not compensatory.

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 uses a specific verb ('Ejecuta') with a clear resource ('múltiples llamadas a la API de Bitrix24') and a distinctive mechanism ('en una sola request HTTP'). This clearly separates it from the many single-call sibling tools like b24_crm_list or b24_tasks_get.

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 makes the intended usage context clear: use this tool when multiple API calls should be batched into one HTTP request, including dependent calls via $result references. It does not explicitly name alternatives or exclusions, but the batching context is strong enough to guide an agent away from single-call siblings.

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