send_file

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

The description discloses the download-then-upload behavior and supports any file type, but lacks details on failure scenarios, size limits, or confirmation of success, which is needed given no annotations.

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 an Args section, but could be slightly more concise by removing redundant phrasing; overall efficient.

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 all parameters and core behavior, but omits return value info (e.g., success indicator) and error handling, which is acceptable for a simple action tool.

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 fully compensates by explaining each parameter: target as group/QQ number, file_url as direct download URL, file_name as optional with default extraction, and target_type options.

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 it downloads a file from a URL and sends it to a group or private chat, distinguishing it from siblings like send_message or send_image that handle local content.

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 specifies target_type for group vs private, providing usage context, but does not explicitly compare to alternative send tools or state when not to use this tool.

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