bitrix_call

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

With no annotations, the description bears full responsibility for disclosing behavior. It simply states 'call directly' without mentioning error handling, authentication requirements, rate limits, return value format, or side effects. This leaves the agent uncertain about what to expect when invoking arbitrary methods.

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 sentence with no wasted words, directly stating the tool's core function. It is front-loaded and efficiently communicates the essential purpose, making it excellent from a conciseness standpoint.

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 raw API wrapper with no annotations, no output schema, and many sibling tools, the one-line description is insufficient. It fails to explain when to use this tool, what kind of response to expect, or any operational constraints, leaving significant gaps in the agent's ability to decide and invoke correctly.

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 input schema fully documents both parameters with examples and descriptions (100% coverage), so the tool description adds nothing beyond the schema. Per the rubric, a baseline of 3 is appropriate when schema coverage is high, even though the description itself contributes no parameter-specific meaning.

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 states the tool calls any Bitrix24 REST API method directly, with a specific verb and resource scope. It implies differentiation from sibling tools by being a generic raw API access, but it doesn't explicitly name alternatives or detail when the specialized tools should be preferred.

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?

No guidance is provided on when to use this tool versus the many specialized sibling tools. The phrase 'directly' suggests using it as a fallback, but there is no explicit mention of preferring dedicated tools when available, nor any context for when this is appropriate.

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