bitrix_test_connection

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states what is checked but does not disclose whether the operation is non-destructive, what a successful or failed result looks like, or whether it performs any actual API call beyond a health check.

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?

A single, tightly scoped sentence with no filler. The main verb and resource are front-loaded, and every word contributes to the tool's meaning.

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 zero-parameter connectivity check, the description is largely sufficient: it says what connection is being tested and which APIs are checked. However, without annotations or an output schema, it would benefit from at least a note about expected behavior or return format to be fully self-contained.

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 tool has zero parameters, so the schema already covers everything. The description adds useful context about what the connection test validates, which is appropriate for a parameterless tool.

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 a specific verb ('проверить' — check), a specific resource (Bitrix24 connection via incoming webhook), and the exact scope (availability of Tasks and CRM REST APIs). It is clearly distinguishable from the sibling tools, none of which are connectivity tests.

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 purpose implies the obvious use case: verify Bitrix24 connectivity before relying on other Bitrix tools. However, there is no explicit guidance about when to use it versus alternatives, no prerequisites, and no statement about when it is not needed.

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