send_file

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

No annotations are present, so the description must disclose behavioral traits. It explains topic/reply behavior but omits side effects such as upload mechanics, file size limits, permission requirements, or return values. 'Send' implies mutation without detailing consequences.

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 first gives the purpose, the second adds two important parameter behaviors. The structure is front-loaded and every clause earns its place.

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?

For a tool with 5 parameters, no annotations, and no output schema, the description leaves basic parameter semantics and behavioral side effects implicit. It handles the tricky forum/reply case well but is incomplete overall.

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 description coverage is only 40%, and the description adds meaning by linking reply_to to topic_id ('within that topic'). It largely paraphrases the schema's topic_id/reply_to descriptions and does not explain chat_id, file_path, or caption semantics, so compensation is partial.

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?

States a specific action ('Send') and resource ('file or photo') with a clear target ('to a chat'), which distinguishes it from siblings like send_voice or send_location. It does not explicitly contrast with send_message, but the resource type makes the purpose clear.

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?

Provides concrete usage guidance for special cases: passing topic_id in forum supergroups and combining reply_to with topic targeting. However, it does not say when to prefer send_file over alternative send tools or when not to use it.

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