apple_music_list_tracks

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint, and openWorldHint. The description adds useful behavioral context by stating that track IDs are persistent hexadecimal IDs, which helps an agent reason about follow-up calls. It does not describe pagination or return shape, but the annotations carry the safety profile.

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 with no filler. It communicates the read-only nature and scope immediately, and every element presents useful information.

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?

There is no output schema, and the schema itself has no parameter descriptions. For a paginated list tool with limit, offset, and playlistId, the description should clarify pagination behavior and return shape. Instead it provides only a high-level scope, leaving significant gaps for correct invocation.

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 compensate for all three parameters. It implies that playlistId exists by mentioning 'library or playlist,' but limit and offset are never explained, nor are defaults, bounds, or pagination semantics.

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 ... track metadata' from the Music library or a playlist. It distinguishes the resource from sibling tools like apple_music_list_playlists and apple_music_get_track, though it does not explicitly name those alternatives.

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 the tool is used when track metadata from the library or a playlist is needed, but it gives no explicit when-to-use guidance or comparison to alternatives such as apple_music_search or apple_music_get_track. Usage is inferable but not spelled out.

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