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

With no annotations present, the description carries full responsibility for exposing behavior. It only mentions billing and nothing about the data shape, whether it lists groups/albums, pagination, or any side effects.

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 short but under-specified; the first sentence is essentially the tool name and the billing sentence is unrelated to tool behavior. It is not a case of efficient conciseness but of missing substance.

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?

Given one parameter, no output schema, no annotations, and a large sibling cluster, this description fails to explain what the endpoint returns or how to meaningfully use the id. An agent has almost no basis for invoking this tool correctly.

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 covers 100% of the parameter with the description 'Artist ID', so the baseline is 3. The tool description adds no extra meaning for the id parameter.

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 essentially restates the name ('Artist appears on') and adds no clarifying verb or resource detail. It does not state what data is returned or how it differs from sibling tools like get_v1_1_artist_discovered_on or get_v1_1_artist_featuring.

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 use this tool versus its many artist-related siblings. The billing sentence is about payment mechanics, not selection context.

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