Bitrix24 MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions monitoring activities but fails to describe what the tool returns (e.g., metrics, summaries, raw data), whether it's a read-only operation, any performance implications, or error conditions. This is a significant gap for a tool with 7 parameters and no output schema.

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, efficient sentence that lists the monitored activities without unnecessary words. It's appropriately sized for the tool's scope, though it could be slightly more structured (e.g., by grouping related activities).

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?

Given the tool's complexity (7 parameters, no annotations, no output schema), the description is incomplete. It lacks details on return values, behavioral traits (e.g., read-only vs. mutation, performance), and differentiation from siblings, making it insufficient for an agent to fully understand the tool's context and usage.

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 has 100% description coverage, clearly documenting all 7 parameters with defaults and optionality. The description adds no parameter-specific information beyond what's in the schema, so it meets the baseline of 3 for adequate schema coverage without extra value.

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's purpose with a specific verb ('monitor') and resource ('user activities'), listing the types of activities tracked (calls, emails, timeline interactions, response times). However, it doesn't explicitly differentiate from sibling tools like 'bitrix24_monitor_sales_activities' or 'bitrix24_get_user_performance_summary', which prevents a perfect score.

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 provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites, context, or comparison to sibling tools (e.g., 'bitrix24_monitor_sales_activities' or 'bitrix24_get_user_performance_summary'), leaving the agent without usage direction.

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