b24_telephony_statistics

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

Annotations already indicate the tool is read-only, idempotent, and non-destructive. The description adds valuable behavioral details: pagination with offset, auto-pagination with fetch_all and a default page cap (40 pages = 2000 records), and the structure of the response (pagination envelope, key fields). No contradictions with annotations.

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 concise: a single introductory sentence followed by a brief enumeration of filter keys and return format. Every sentence adds value, no redundancy, and it is front-loaded with the core purpose.

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 that an output schema exists and all parameters are described in the schema, the description adequately covers what the tool does, including pagination behavior and common filters. It provides sufficient context for an agent to use the tool correctly without missing critical information.

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% coverage, so each parameter's description is already present. The tool description adds context by listing commonly used filter keys (e.g., '>=CALL_START_DATE', 'PORTAL_USER_ID') with examples and indicating the response fields (CALL_ID, duration, etc.). This enhances understanding beyond the schema alone.

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 lists call statistics using the Bitrix24 voximplant.statistic.get API, with pagination. It distinguishes itself well from sibling tools, which are mostly CRM or task-related, by focusing on telephony statistics specifically.

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 common filter keys and pagination details, which gives some usage context, but it does not explicitly state when to use this tool versus alternatives (e.g., b24_call for single call initiation). No direct alternative exists among siblings, but guidance on when not to use it is missing.

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