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

No annotations are provided, so the description carries full responsibility. It discloses only billing credits but nothing about data returned, side effects, or API behavior. The phrase 'appears on' is ambiguous and does not clarify what the response contains.

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 extremely brief, but brevity is not conciseness when it omits necessary information. It front-loads the title redundantly and wastes the opportunity to explain purpose. Every word is technically short, but the description is under-specified.

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 simple tool with one parameter and no output schema, the description still fails to specify what the tool returns, the nature of 'appears on' (e.g., tracks, albums, compilations), or any behavior. The sibling constructor shows ambiguity about its scope, so this is incomplete.

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 schema already provides a description for the 'id' parameter ('Artist ID') and an example, giving 100% coverage. The description adds no additional parameter meaning, so the baseline score of 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 simply restates the title 'Artist appears on' with no verb or defined action. It adds only 'Group: Artists' and billing info, giving no indication of what the tool actually does (e.g., listing albums/compilations where the artist appears). This is essentially a tautology.

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 provided on when to use this tool versus sibling tools like get_v1_1_artist_albums or get_v1_1_artist_discography_overview. There is no context about typical use cases or exclusions.

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