Artist

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

Annotations declare readOnlyHint=false, openWorldHint=true, and idempotentHint=false, so the safety profile is partly covered. The description adds genuinely valuable context beyond that: it discloses financial cost (paid API credits) and explains why a non-readonly annotation applies to what is effectively a read ('read-like POST requests do not publish to social platforms'). It stops short of stating rate limits or return shape.

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?

Three short sentences with the purpose front-loaded and cost/confirm constraints immediately after. The closing sentence about social platforms is slightly tangential but is what reconciles the readOnlyHint=false annotation, so it earns its place.

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, so the field enumeration in the description usefully substitutes for return-value documentation. Combined with annotations and 100% schema coverage, an agent has enough to call this correctly, though it lacks any note on pagination, error behavior, or response size.

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 all four parameters (id, url, account, confirm) are already documented at the schema level. The description only restates the confirm=true requirement and adds nothing about the id-vs-url precedence or the account parameter. Baseline 3 is appropriate when the schema carries the load.

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?

States a specific verb (Retrieves) plus a precise resource (Apple Music artist details) and enumerates exactly which sections are returned (artwork, editorial notes, top songs, albums, music videos, playlists). This makes it trivially distinguishable from sibling tools like apple_music_album, apple_music_track, and apple_music_search.

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 surfaces two operative prerequisites — credit consumption and confirm=true — which tell the agent how to invoke it safely. However, it never says when to choose this over alternatives such as apple_music_search or spotify_artist, nor when the call is inappropriate, so usage is only implied.

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