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 'monitors' activities, which implies a read-only operation, but doesn't clarify whether this requires specific permissions, what format the monitoring output takes, whether it's real-time or historical, or any rate limits. For a monitoring tool with 7 parameters and no annotation coverage, this leaves significant behavioral gaps.

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 clearly states the tool's purpose. There's no wasted language or unnecessary elaboration. However, it could be slightly more structured by front-loading the most critical information about scope or differentiation from sibling tools.

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 monitoring tool with 7 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what the monitoring output looks like, how results are structured, whether there are pagination considerations, or what behavioral constraints exist. The agent would need to invoke the tool to understand its full behavior and output format.

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, with all 7 parameters well-documented in the schema itself. The description mentions 'tasks, follow-ups, and meetings' which aligns with some parameters (includeTaskCompletion, includeFollowUpTracking, includeMeetingTracking), but doesn't add meaningful semantic context beyond what the schema already provides. The baseline score of 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: 'Monitor sales-related activities including tasks, follow-ups, and meetings'. It specifies the verb ('monitor') and resource ('sales-related activities'), but doesn't explicitly differentiate it from the sibling tool 'bitrix24_monitor_user_activities', which appears to have a broader scope. The description is specific about what types of activities are monitored.

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 any prerequisites, constraints, or compare it to sibling tools like 'bitrix24_monitor_user_activities' or 'bitrix24_generate_sales_report'. The agent must infer usage from the tool name and description alone without explicit context.

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