send_file

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

The description adds useful behavioral context beyond the annotations, such as Telethon auto-detecting the file type, voice_note requiring .ogg/.mp3, and ttl_seconds being PM-only. This enriches the agent's understanding of side effects and constraints, though it doesn't cover potential errors or upload behavior.

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 well-structured with a one-line purpose followed by a clear bulleted parameter list. It is appropriately sized for 13 parameters, with each bullet earning its place. Slightly verbose but not wasteful.

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?

The description covers the tool's core function and all parameters, including behavioral nuances. Because an output schema exists, missing return details are not critical. It lacks explicit error handling or upload progress details, but overall it's sufficient for an agent to invoke the tool correctly.

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 input schema provides only titles and types with no descriptions, while the description explains every parameter's meaning and constraints (e.g., force_document, voice_note, ttl_seconds). This is a complete and valuable addition beyond 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 'Отправить файл' (send file) and specifies that Telethon will auto-determine the type. While it is a specific verb+resource, it does not explicitly distinguish itself from sibling tools like send_voice or send_video_note, which are more specialized.

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?

There is no guidance on when to use this tool versus alternatives like send_voice, send_video_note, or send_album. The description only explains the tool's own parameters, not the appropriate context for choosing it over siblings.

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