send_local_audio_or_voice

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

With no annotations at all, the description carries the full behavioral burden for a send/write tool, yet it never states whether file_path must exist on the bot's own filesystem, what happens when chat_id is omitted, size or duration limits, or that the call is a mutating action. The only behavioral hint is the OGG/Opus encoding recommendation, which is thin for an upload operation.

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 English lead is front-loaded and efficient, but the Chinese paragraph largely restates it while silently adding the title/performer detail, so a reader who only reads the first sentence misses information. The bilingual split is reasonable but the redundancy costs clarity.

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?

Contextual completeness is judged relative to a tool with no annotations, eight undocumented parameters and an output schema that already covers return values. Given those constraints the description should explain chat_id defaults, duration and inline_buttons, none of which appear, so it is insufficient for an agent to call the tool correctly without guessing.

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 0% across 8 parameters, so the description must compensate, and it only explains mode, title and performer. caption, chat_id, duration and inline_buttons receive no explanation anywhere, leaving half the surface undocumented.

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 names a specific verb and resource ('Send a local audio file') and splits the result into two clearly labelled presentations, music track vs native voice note, so an agent can tell it apart from the video/photo/document siblings by file type. It stops short of explicitly contrasting itself with those siblings, which keeps it at 4 rather than 5.

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?

Mode selection is implied through outcome ('mode=audio 以音樂曲目呈現' vs 'mode=voice 以原生語音訊息呈現') and a codec recommendation is given, which is useful context for choosing voice mode. However, there is no explicit when-to-use / when-not-to-use against send_local_document or send_local_video, and no stated prerequisites such as file size limits or whether the path is server-local.

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