Bitrix24 MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'track' implies a read operation, it doesn't clarify whether this requires specific permissions, what data format is returned, whether it's paginated, or if there are rate limits. The mention of 'timing analysis' hints at calculations, but doesn't specify if these are performed server-side or require client-side processing. For an analysis tool with 8 parameters and no annotation coverage, this is insufficient.

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 without unnecessary words. Every word earns its place: 'track' (action), 'deal progression' (resource), 'through pipeline stages' (scope), 'with timing analysis' (capability). There's zero waste or redundancy.

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 (8 parameters, analysis functionality) and absence of both annotations and output schema, the description is minimally adequate. It identifies the tool's purpose but doesn't address behavioral aspects, return format, or usage context that would help an agent understand what to expect from invocation. The 100% schema coverage helps, but for an analysis tool without output schema, more guidance would be beneficial.

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 8 parameters thoroughly with descriptions and defaults. The description adds no additional parameter semantics beyond what's in the schema - it doesn't explain relationships between parameters (e.g., how dealId interacts with other filters) or provide usage examples. With complete schema coverage, the baseline 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 'Track deal progression through pipeline stages with timing analysis', which includes a specific verb ('track'), resource ('deal progression'), and scope ('pipeline stages with timing analysis'). It distinguishes from siblings like 'bitrix24_list_deals' or 'bitrix24_get_deal' by emphasizing progression tracking and analysis rather than simple listing or retrieval. However, it doesn't explicitly differentiate from all potential overlapping tools like 'bitrix24_monitor_sales_activities'.

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, when this tool is preferred over similar tools like 'bitrix24_list_deals' or 'bitrix24_monitor_sales_activities', or any constraints on usage. The agent must infer usage from the purpose alone without explicit direction.

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