telegram_send_audio

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

Annotations already indicate non-read-only, non-destructive, non-idempotent behavior. The description adds context on accepted audio sources (local file, URL, file_id) and return format. No contradictions, but no extra behavioral details like rate limits or auth.

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?

Four concise sentences with immediate purpose, then accepted inputs, then params, then return. No redundant or irrelevant information.

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 the nested input schema and available output schema, the description sufficiently covers input types, required fields, and return format. It lacks details on error handling or size limits, but is adequate 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?

The description lists sub-properties (chat_id, audio source, optional caption/performer/title) but the schema already provides detailed descriptions for each. With schema coverage 0% at the top level, the description adds minimal value beyond what is in the schema.

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 'Send', the resource 'audio file', and adds context 'shown as music player'. This distinguishes it from sibling tools like telegram_send_voice or telegram_send_video.

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 implies usage for sending audio files but does not explicitly contrast with other media tools or provide when-to-use guidance. It lists accepted input types but lacks exclusions.

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