bitrix24_voximplant_statistic_get

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

With no annotations, the description fully discloses key behaviors: one row per call, explanation of fields, null status of TRANSCRIPT fields (verified), limitation of REST API vs UI, and authoritative claim for direction/duration.

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?

Well-structured and informative, but somewhat long. Each sentence adds value, so no waste; still, a slightly more compact format could be slightly better.

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?

No output schema, but the description explains key return fields and provides a complete workflow for understanding a call. Covers filtering, limits, and behavioral notes, making it fully actionable.

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 coverage is 100%, but the description adds significant value with concrete examples of filter values, date-bound syntax, and explanation of output fields, exceeding what the schema alone provides.

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?

Starts with a clear verb+resource: 'Get telephony call statistics (Mango Office / Voximplant) — one row per call.' and distinguishes from siblings by providing workflow guidance referencing other tools.

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?

Explicitly states when to use this tool (to get call stats) and when to use alternatives (bitrix24_crm_timeline_note_get, bitrix24_call_transcribe) for transcript/recording. Provides authoritative guidance on direction/duration.

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