getLikeList

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

No annotations are present, so the description carries the transparency burden. It does disclose an authentication requirement (Token and user request header), which is useful operational context. However, it does not state whether the list is for the authenticated user only, how pagination behaves, or what response shape is returned.

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 states the action and resource while also mentioning the key auth requirement. No filler or redundancy.

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 output schema and no annotations, the description leaves important context undefined: whose like list is returned (token owner vs any user), what the response contains, and how offset/limit pagination works. The sibling tools all use byUserId, so the absence of a userId parameter makes the target user ambiguous.

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 explains all four parameters. The description only repeats Token and userAgent and adds no semantic detail beyond the schema, such as offset/limit behavior or the meaning of 'userAgent'.

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 a get operation on a specific resource ('点赞列表' / like list) for the Shendao platform, using '获取'. It does not explicitly distinguish this from sibling list tools such as getFavoriteListByUserId or getRecentlyPlayListByUserId, but the resource name itself is reasonably distinct.

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?

No guidance is given about when to choose this tool over sibling tools, nor are exclusions or prerequisites beyond the mention of Token and userAgent. The usage context is only implied by the tool name and the resource term.

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