Bitrix24 MCP Server

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 mentions analysis of 'patterns' and 'health' but doesn't describe what the tool actually does—whether it performs calculations, returns metrics, generates reports, or has side effects. There's no information on permissions, rate limits, or output format, leaving significant gaps for a tool with 9 parameters.

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 with zero waste—'Analyze customer engagement patterns and relationship health'. It is appropriately sized and front-loaded, though its brevity contributes to gaps in other dimensions. Every word earns its place in conveying the core function.

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 complexity (9 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain what the analysis entails, what data it uses, or what the output looks like. For a tool with multiple boolean flags controlling analysis components, more context is needed to guide effective use, especially without annotations or output schema.

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%, so the schema fully documents all parameters with descriptions, defaults, and enums. The description adds no additional meaning beyond implying analysis of 'engagement patterns' and 'relationship health', which loosely maps to parameters like 'includeEngagementScores' and 'includeRelationshipHealth'. Baseline 3 is appropriate as the schema does the heavy lifting.

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 'Analyze customer engagement patterns and relationship health' states the general purpose but lacks specificity. It mentions the verb 'analyze' and the domain 'customer engagement' but doesn't specify what resources or data sources are used, nor does it differentiate from sibling tools like 'bitrix24_analyze_account_performance' or 'bitrix24_monitor_sales_activities'. The purpose is clear but vague about scope and methodology.

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. With many sibling tools for analysis, monitoring, and reporting (e.g., 'bitrix24_analyze_account_performance', 'bitrix24_generate_sales_report'), there is no indication of specific use cases, prerequisites, or exclusions. The agent must infer usage from the tool name and parameters alone.

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