set_qq_avatar

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

With no annotations, the description carries the full behavioral burden, and it only discloses that the change applies to the currently logged-in account. It does not say the existing avatar is overwritten irreversibly, whether a login/authentication state is required, what happens on invalid input, or any rate limits. This is a mutation tool with essentially no safety or side-effect disclosure.

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 short and front-loads the core action before the API name and parameter note. The ':param file:' line duplicates the schema description, which is slight waste, but the overall length is appropriate for a one-parameter tool.

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 simple one-parameter tool with no output schema, the description covers the action, the target account, and the accepted input formats. It stops short of noting overwrite behavior or error conditions, but nothing essential for correct invocation is missing.

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 100%, so the single parameter is already fully documented in the schema, and the description merely repeats the same text verbatim. No added meaning (e.g., size limits, accepted image formats, fallback behavior for URLs) is provided beyond the structured field, so the baseline 3 applies.

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 — modifying the avatar of the currently logged-in QQ account — and the scope qualifier '当前登录' disambiguates it from siblings like set_group_portrait or set_qq_profile. It is clear what the tool does, though it never names an alternative explicitly.

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?

There is no when-to-use or when-not-to-use guidance and no mention of alternative tools such as set_qq_profile or set_group_portrait. The agent must infer that this is the tool for avatar changes purely from the name and verb.

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