List artist albums

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering safety and network behavior. The description adds the pagination behavior ('Page through'), which is useful context beyond annotations, but omits auth needs, rate limits, or response structure.

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 sentence that earns its place with no filler. It conveys the tool action and pagination scope efficiently.

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 list tool with an output schema and safety annotations, the description is minimally complete. However, with 0% schema description coverage, it should say more about pagination parameters and differentiate from sibling album-listing tools.

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 0%, so the description must carry parameter meaning. It only implies pagination through 'Page through,' but does not explain limit, offset, defaults, or the artist_id format, leaving most parameter semantics to inference from names and constraints.

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 states a clear verb ('Page through') and resource ('an artist's main album discography'), which distinguishes it from sibling tools for EPs/singles and other albums. It does not explicitly name those siblings, but the scope is specific enough to identify the tool's job.

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?

Usage is implied by 'main album discography' and 'Page through,' suggesting this tool is for main albums with pagination. It does not explicitly state when to use it versus alternatives like tidal_get_artist_ep_singles or tidal_get_artist_other_albums, leaving the agent to infer.

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