Send Telegram Document

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

Annotations indicate this is not read-only or destructive, and the description adds context: Telegram fetches the file server-side, returns a confirmation with message_id, and describes common errors. These details go beyond annotations without contradiction.

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, well-structured with clear sections (main purpose, Args, Returns, Error Handling), and front-loaded with the most important information. Every sentence adds meaningful content.

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 lack of an output schema, the description adequately explains the return value (confirmation with message_id) and common errors. All parameters are documented, and the tool's behavior regarding file size and accessibility is covered. It is 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?

The schema has 100% coverage with descriptions, so baseline is 3. The description adds value by listing parameters in a structured 'Args' block and clarifying that the document URL must be public HTTPS and that caption has a 1024-character limit, which slightly exceeds the schema's own descriptions.

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 sends a file (PDF, CSV, ZIP, etc.) to a Telegram chat via URL with an optional caption. It provides a specific verb-resource pair ('send a file') and distinguishes from siblings like telegram_send_photo and telegram_send_message.

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 implicitly indicates when to use (sending documents by URL) but does not explicitly exclude cases like sending local files or when to use alternatives. It includes helpful error handling guidance and a size limit, which aids in correct usage.

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