telegram_send_file

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

The description explicitly states 'This changes external state,' which complements the annotations readOnlyHint=false. It also adds a meaningful safety condition requiring explicit user confirmation, going beyond what annotations provide.

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?

Two sentences with no filler. The primary action is stated first, and the critical side-effect warning and user-confirmation requirement are included without redundancy.

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 action, side effect, and consent gate, which is sufficient for a simple send-file tool. It does not describe response or error behavior, but this is not essential for correct invocation given the straightforward parameter schema.

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?

With 0% schema description coverage, the description must compensate for parameter meaning. It maps 'recipient, file, and caption' to chat_id, file_path, and caption, but it does not explain what a chat_id is, what file_path should contain, or any path/type requirements.

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 states a specific verb and resource: 'Send a local file through the personal Telegram account.' This clearly differentiates the tool from siblings like telegram_send_message, telegram_reply_message, and telegram_download_file.

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 gives an explicit usage condition: 'call only after the user explicitly confirms recipient, file, and caption.' This is clear contextual guidance, though it does not explicitly mention alternatives or when not to use the tool.

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