set_friend_add_request

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. It conveys that approve=false rejects and that remark is applied after approval, but says nothing about permissions, whether a rejection is final/irreversible, or what happens to the pending request state.

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 purpose is front-loaded in a single clear sentence, and the docstring-style parameter lines are compact. The :param lines duplicate the schema descriptions, which is mild redundancy rather than bloat.

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?

With no annotations and no output schema, the description should disclose the mutation's safety profile and expected result, and it only partially does so. It is adequate for a simple 3-parameter approval action but leaves the agent guessing about reversibility and the return value.

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 the description merely restates the same per-parameter text verbatim (flag, approve, remark). It adds no format, source, or constraint detail beyond the schema, 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+resource: approving/handling incoming friend-add requests, with the OneBot 11 action name given for traceability. It is clearly distinguishable from the sibling set_group_add_request by resource (friend vs group), though it does not explicitly name that sibling.

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?

Usage is implied: you call this when you have a pending friend request and want to accept or reject it, and the 'flag' note hints it comes from an event report. However, it never names where to obtain the flag (e.g. get_recent_notices_and_requests) or states any when-not conditions.

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