bitrix_get_deal

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

With no annotations, the description carries the full behavioral disclosure burden. 'Получить полную информацию' clearly indicates a read operation returning deal data, but it does not describe behavior such as error handling, authorization requirements, or what 'full' information includes. The description is adequate but does not go beyond the obvious.

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 a single, front-loaded sentence that immediately states the verb, resource, and identifier. There is no filler, and every part of the sentence 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 simple getter with one fully documented parameter and no nested objects, the description adequately conveys purpose and scope. It does not provide the return structure, but no output schema exists and the tool is low-complexity, so the gap is minor.

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% — the schema already documents dealId as 'ID сделки.' The description only restates that the tool works by ID and adds no extra meaning, format detail, or behavioral nuance beyond the schema, so 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?

Description states a specific action ('get full information') on a specific resource ('deal') by a specific key ('ID'). It is clearly differentiated from siblings like bitrix_list_deals, bitrix_create_deal, and bitrix_update_deal, so an agent can tell what this tool is for without opening the schema.

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 phrase 'по ID' implies the tool is for fetching a single deal when its ID is known, which provides implied usage context. However, it does not explicitly mention alternatives (e.g., bitrix_list_deals) or state when-not to use the tool, so usage guidance is only implied rather than explicit.

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