set_friend_add_request

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

With no annotations, the description bears the full behavioral burden. It does disclose that approve=true accepts and approve=false rejects, but it never says whether the flag expires, whether a rejection is reversible, what permissions are needed, or what the caller receives — significant gaps for a mutation tool with zero annotation coverage.

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 one-line purpose is front-loaded and the parameter block is terse; total length is small. The only waste is that the param lines duplicate the schema word-for-word rather than adding value.

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 three-parameter mutation tool with no annotations and no output schema, the description covers what the tool does and what the parameters mean but omits how to obtain the flag, the effect of approving/rejecting on the target's friend list, and any error conditions — leaving an agent without enough context to invoke it safely.

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 schema already documents flag, approve, and remark. The :param block in the description merely restates those identical texts verbatim, adding no format hints, flag provenance, or constraint details beyond the structured data.

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 pair — approving/handling an incoming friend-add request — and cites the underlying OneBot 11 action. That resource (friend add request) is implicitly distinct from the sibling set_group_add_request, though the description never names that sibling to sharpen the distinction.

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 by the subject ('someone sent you a friend request'), but there is no explicit when-to-use guidance, no indication of where the required 'flag' comes from, and no mention of the obvious alternative (set_group_add_request) or the retrieval tool (get_recent_notices_and_requests).

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