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 states the tool compares performance metrics but doesn't explain what 'performance metrics' entail, how the comparison is presented (e.g., as a report, ranking, or chart), whether it's a read-only operation, or if it has any side effects like data aggregation. This leaves significant gaps in understanding the tool's behavior beyond the basic action.

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 directly states the tool's purpose without any fluff or redundancy. It's front-loaded with the core action and resource, making it easy for an agent to parse quickly. Every word earns its place, achieving optimal conciseness.

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 of comparing multiple users with various metrics and options, the description is insufficient. It lacks output schema, and with no annotations, it doesn't cover behavioral aspects like return format (e.g., structured data, visual report), error handling, or performance implications. For a tool with 6 parameters and no structured output, more context is needed to guide effective 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, providing clear details for all parameters (e.g., user IDs as an optional array, date formats, metric enums, and boolean flags). The description adds no additional semantic context beyond what's in the schema, such as explaining what 'performance rankings' or 'trend analysis' mean in practice. Since the schema does the heavy lifting, the baseline score of 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?

The description clearly states the tool's purpose as 'Compare performance metrics between multiple users,' which specifies the verb (compare) and resource (performance metrics between users). However, it doesn't explicitly differentiate from sibling tools like 'bitrix24_get_user_performance_summary' or 'bitrix24_analyze_account_performance,' which might have overlapping functionality, so it doesn't reach the highest 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. It doesn't mention prerequisites, such as needing user IDs or date ranges, or compare it to siblings like 'bitrix24_get_user_performance_summary' for individual user analysis or 'bitrix24_analyze_account_performance' for broader metrics. This lack of context leaves the agent to infer usage scenarios.

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