itunes_get_artist_albums

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It indicates a search operation (presumably read-only) and notes the limit parameter's default and max, but it does not explicitly state that the operation is non-destructive, mention pagination, or describe the return format. Still, for a simple search, the behavior is largely inferable from the description.

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 concise: one sentence for purpose and a compact arg list. It is front-loaded and free of fluff, efficiently conveying the necessary information without wasted words.

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 two parameters and no output schema, the description covers the core purpose and parameter semantics adequately. It might benefit from explicit usage guidance or a note about the return being a list of albums, but overall it is sufficiently complete for an agent to understand and invoke the tool.

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?

With schema description coverage at 0%, the description compensates by explaining both parameters: artist is the name to search for, and limit is the number of albums with a default of 10 and max of 25. This adds meaning beyond the bare schema, though it could include more detail (e.g., case sensitivity or matching behavior).

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 uses a specific verb ('Search') with a clear resource ('Apple Music's global catalog') and object ('official albums by any artist'), making the tool's purpose immediately clear. It distinguishes from siblings like itunes_get_artist_top_tracks (tracks) and itunes_search (generic search) by focusing specifically on albums by an artist.

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 for retrieving albums by an artist but does not explicitly state when to use this tool over alternatives like itunes_get_artist_top_tracks or itunes_search_catalog. No exclusions or 'use this when' guidance is provided, though the purpose alone makes it fairly obvious.

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