get_friends_with_category

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing beyond the name. It does not indicate pagination, rate limits, ordering, or what happens when the endpoint is unavailable; the only added signal is that this is a NapCat extension rather than standard OneBot. For a zero-param read this is low risk, but the disclosure is still minimal.

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?

One short sentence that front-loads the function and tucks the endpoint identity into a parenthetical. The parenthetical partially restates the tool name already visible to the agent, but it also contributes the 'NapCat extension' tag, so waste is minor.

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 zero-param read with no output schema, the description is adequate but does not explain the shape of the returned grouping (how categories and their members are represented), which the absent output schema leaves entirely open. It does correctly imply the result is categorized rather than flat.

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?

The tool takes zero parameters, so there is no parameter semantics for the description to supply; the baseline of 4 applies. Nothing is misleading or inconsistent with the empty schema.

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 verb and resource ('获取好友列表') plus a scope qualifier ('按好友分组归类'), which implicitly separates it from the flat sibling get_friend_list. The parenthetical identifies it as a NapCat extension endpoint, reinforcing what it is. It never names get_friend_list explicitly, so the differentiation is left to inference.

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 gives no when-to-use guidance: it does not say to prefer this over get_friend_list when category/group data is needed, nor when it is unnecessary. No prerequisites, no alternatives, no exclusions are offered.

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