getFriendListByUserId

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

No annotations are provided, so the description carries full burden for behavioral disclosure. However, it only restates the tool's name and does not mention pagination, default limits, error handling, authentication requirements, or any other behavioral traits. This is a significant gap for a tool that likely returns a list.

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 a single, front-loaded sentence that succinctly states the tool's purpose without unnecessary filler. It is appropriately sized for the tool's simplicity.

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 tool is simple, and the schema covers the parameters, but there is no output schema and no annotations. The description lacks usage guidance and expected return behavior, which might be incomplete for an agent deciding between this and similar sibling tools. It is adequate but not rich.

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 input schema has 100% description coverage, clearly explaining each parameter (offset, limit, userId). The description adds no additional parameter context beyond what the schema already provides, which is acceptable given the high schema coverage.

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 clearly states the tool retrieves a friend list by user ID, using a specific verb (获取) and resource (好友列表). It distinguishes itself from sibling tools like getFollowerListByUserId and getFollowingListByUserId by specifying 'friend list' rather than followers or following.

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 implies usage when a user's friend list is needed, but provides no explicit guidance on when to prefer this tool over similar sibling tools (e.g., getFollowerListByUserId). There are no alternatives mentioned or exclusions stated.

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