get_artist_singles

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

With no annotations, the description must carry the behavioral disclosure burden. It does convey that this is a read-only list operation via GET and adds a useful quota signal ('Quota: 🟢 single'). It does not describe return format, pagination behavior, or whether only singles are returned versus other album groups, but the quota and endpoint provide meaningful operational context.

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?

Two compact, information-dense sentences. The core purpose is front-loaded, and the endpoint plus quota signal are included without any filler or redundant restatement of the tool name.

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 straightforward filtered list operation, the description is largely complete: full schema coverage handles parameter semantics, and the endpoint plus quota give useful operational context. It lacks any guidance about how this differs from sibling album/discography tools, but that is a minor gap given the clear 'singles only' scope.

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 baseline is 3 even though the description adds little parameter-level detail. The endpoint path does clarify that artist_id maps to the artist path parameter and that include_groups=single is fixed, but limit, offset, market, max_results, and response_format are not elaborated beyond what the schema already provides.

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 specific verb and resource: 'List an artist's singles only' and includes the exact endpoint with the include_groups=single query parameter. It clearly distinguishes this tool from get_artist_albums and other artist-focused siblings by narrowing the scope to singles.

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?

The description implies usage: use this when you need only an artist's singles, not all albums. However, it never explicitly names alternatives such as get_artist_albums or get_artist_discography, nor does it state when NOT to use this tool.

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