get_artistRetrieve an artist's biography and top songs by ID, with optional album list and pagination controls.
获取歌手简介和热门歌曲，可选附带专辑列表。
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | 歌手 ID（数字） | |
| top_songs | No | 返回的热门歌曲数量，默认 20，最多 50 | |
| album_limit | No | 专辑数量，默认 20 | |
| album_offset | No | 分页偏移量，默认 0 | |
| include_albums | No | 是否同时返回专辑列表 |
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds nothing beyond that: no mention of album pagination behavior despite limit/offset params, no rate-limit or error context for an open-world remote API, no indication of what the payload resembles.
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?
A single front-loaded clause with no filler or redundancy. It is efficient, though the terseness leaves it thin rather than richly structured.
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 read-only detail tool with fully described params and no output schema, naming the three returned sections (bio, top songs, albums) is the minimum needed. It omits how album and song lists are shaped or paginated, which matters given the limit/offset parameters.
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 all five parameters (including defaults, min/max bounds, and the top_songs cap of 50) are already documented. The description only echoes the include_albums toggle, adding no syntax or interaction detail beyond the 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?
Specific verb+resource: fetches artist bio, top songs, and optionally albums. The scope is clear enough to distinguish it from get_album and get_song_detail, though it never names those siblings explicitly.
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 on when to use this versus get_album, get_song_detail, or search, and no prerequisite noted (e.g., that an artist ID must first be obtained via search). The agent must infer all routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.