set_qq_profile

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Set' with no information about side effects, permissions, whether omitted parameters preserve existing values, whether an empty call is a no-op, or what response to expect.

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 but not meaningfully concise because it repeats the tool name without providing any additional information. It does not earn its place: a one-line tautology is under-specification rather than efficient writing.

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 schema fully describes the three optional parameters, but the description itself provides almost no surrounding context. An agent can infer basic intent from the name, but nothing explains the scope, mutation semantics, or behavior when no parameters are provided, so the description is not complete enough for a mutation tool with no annotations.

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%, and each parameter already has a clear description in the schema. The tool description adds no additional parameter meaning, but the baseline of 3 applies because the schema fully documents the parameters.

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 'Set QQ profile' is essentially a verbatim restatement of the tool name and does not clarify that this is the current user's personal profile, what aspects it changes, or how it differs from profile-like sibling tools such as set_group_card or set_group_name. It names a resource and an action but adds no specificity beyond the name itself.

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 guidance about when to use this tool versus alternatives. With many sibling tools that modify group-level profile fields, an agent gets no help deciding whether set_qq_profile is the right choice for a given request.

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