bitrix24_call_transcribe_fast

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

Discloses key behaviors: runs locally, trade-offs (lowercase, no punctuation, no speaker labels), requires Python environment, returns clear error if missing deps, does not write to Bitrix, and brand auto-normalization. No annotations provided, so description carries full burden and excels.

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 with clear front-loading of the tool's purpose. While slightly long, every sentence adds useful information. Could be slightly more concise, but overall efficient.

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?

Covers input, output format, dependencies, error handling, and post-processing. No output schema exists, but description includes return fields. Complete for the tool's complexity.

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% for the single parameter `activityId`. Description adds context that it is a VOXIMPLANT_CALL activity, which aids understanding beyond the schema's description.

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?

Clearly states the tool does FAST transcription using GigaAM v2 model, distinguishing it from the default and max tiers. The verb 'transcribe' combined with 'fast' and resource 'CRM call' is specific.

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 says when to use: 'when you want the gist fast/cheap and don't need Whisper's punctuation or the max tier's dual-transcript + diarization.' Also explains the three-tier trade-off and that it does not write to Bitrix, directing to save with another tool.

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