Bitrix24 MCP Server

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

No annotations are provided, so the description carries full burden. It mentions analyzing 'performance and activities' but doesn't disclose behavioral traits like whether this is a read-only operation, what permissions are needed, whether it's computationally intensive, what format the analysis returns, or if there are rate limits. For a 7-parameter analysis tool with no annotations, this is inadequate.

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 front-loads the core purpose. Every word earns its place with no redundancy or unnecessary elaboration. It's appropriately sized for the tool's complexity.

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 7-parameter analysis tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'performance' means in this context, what types of activities are analyzed, what the output looks like, or any behavioral constraints. The agent would struggle to understand the tool's full behavior and output expectations.

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 already documents all parameters thoroughly. The description adds no parameter-specific information beyond what's in the schema (e.g., it doesn't explain what 'performance' metrics are analyzed or what 'activities' include). Baseline 3 is appropriate when 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 clearly states the tool's purpose: 'Analyze performance and activities for specific accounts (companies/contacts)'. It specifies the verb ('analyze'), resource ('accounts'), and scope ('performance and activities'), but doesn't explicitly differentiate from sibling tools like 'bitrix24_analyze_customer_engagement' or 'bitrix24_get_user_performance_summary'.

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, appropriate contexts, or exclusions. With many sibling tools for analyzing performance (e.g., 'bitrix24_analyze_customer_engagement', 'bitrix24_compare_user_performance'), the agent lacks direction on selection criteria.

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