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 'List' implies a read operation, it doesn't specify whether this requires authentication, what permissions are needed, whether results are paginated, or what format the output takes. The mention of 'optional filtering and ordering' hints at capabilities but lacks operational details.

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 extremely concise at just 7 words, front-loading the core purpose ('List deals') immediately. Every word earns its place by adding meaningful information about capabilities ('with optional filtering and ordering').

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 list/read operation with no annotations and no output schema, the description provides basic purpose but lacks important context about authentication requirements, result format, pagination behavior, or how it differs from similar sibling tools. The 100% schema coverage helps, but the description itself leaves significant gaps for agent understanding.

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 description mentions 'optional filtering and ordering' which aligns with the 'filter', 'orderBy', and 'orderDirection' parameters in the schema. However, with 100% schema description coverage, the schema already documents all four parameters thoroughly. The description adds minimal value beyond what's already in the structured schema fields.

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 verb ('List') and resource ('deals'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'bitrix24_get_deal', 'bitrix24_get_deals_from_date_range', or 'bitrix24_get_latest_deals', which all appear to retrieve deals in different ways.

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 mentions 'optional filtering and ordering' which implies some usage context, but provides no explicit guidance on when to use this tool versus the many sibling deal-related tools. There's no mention of alternatives, prerequisites, or specific scenarios where this tool is preferred.

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