qq_send_group_file

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

Description lacks details on behavioral traits such as authorization requirements, side effects, error handling, or limitations on file size/types. With no annotations, the description should fully disclose these, but it does not.

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 sentence, no redundancy, efficiently states the action. Could be improved by front-loading key constraints, but acceptable.

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?

Tool has 3 parameters, no output schema, and no annotations. Description does not explain return values, error conditions, parameter formats, or operational limitations. Incomplete for effective agent use.

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 has 0% coverage, so description must compensate. It implies file can be a local path or URL, but does not specify format for group_id or the name parameter. The optional name is mentioned but not explained. Adds minimal semantic value.

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 uploads a local file or URL to a QQ group, using a specific compatible action. It distinguishes the target (QQ group) from siblings like qq_send_private_file, but does not explicitly contrast with qq_send_group_message.

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?

No guidance on when to use this tool versus alternatives like qq_send_group_message or qq_send_private_file. Missing context for when uploading a file is appropriate.

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