Send file or image

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

Discloses all important behavioral traits: initial call returns draft without uploading bytes, confirm call uploads and sends irreversibly; verification of chat and file against confirmed values; type determination by extension; post-send behavior (reading message and downloading attachment). No contradiction with annotations (destructiveHint=false is consistent with creating a message).

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?

Single paragraph in Russian is information-dense but well-organized. Every sentence adds new information. Could be slightly improved with bullet points or clearer separation of steps, but it remains efficient and front-loaded.

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 tool's complexity (two-step, irreversible, verification), the description covers all necessary aspects: workflow, constraints (no voice/gallery), and post-send retrieval. No output schema, but description compensates by explaining how to download the attachment after sending.

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 covers all 4 parameters with descriptions. The description adds significant value by explaining the two-step workflow for confirm and confirm_token, clarifying that path is absolute, and linking parameters to the behavioral steps. It goes beyond what schema alone provides.

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?

Description clearly states it sends files/images in a two-step process, distinct from siblings like send_message (text) and download_attachment (retrieval). It specifies the verb (send) and resource (file or image) with precise scope (two-step, irreversible).

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?

Describes when to use (sending files/images) and the two-step workflow. It explicitly mentions that voice/gallery types are not sent (only reading). However, it does not explicitly state when not to use this tool in favor of a sibling, though the distinction is clear from context.

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