Get a wide playlist image

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe-read profile is covered. The description adds nothing beyond that – no mention of whether the URL is signed/expiring, whether the playlist must be public, or any auth/caching behavior, which is notable for a URL-fetching tool that makes a network call.

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 tight sentence with the resource and the dimension scoping front-loaded; nothing is wasted. It is arguably under-specified rather than over-long, but the structure itself is efficient.

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?

An output schema exists, so return-value detail is not required from the description, and the core purpose is stated. However, with 0% parameter coverage and a near-identical sibling (tidal_get_playlist_image), the definition leaves the agent without enough to confidently pick or parameterize this 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?

Schema description coverage is 0% for all three parameters. The phrase 'requested dimensions' vaguely gestures at width/height but supplies no defaults, bounds, or units beyond what the schema already encodes, and playlist_id is never mentioned. The description does not compensate for the coverage gap.

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 ('Return a wide playlist-image URL') and the scoping parameter ('at requested dimensions'), which distinguishes it from the square-image sibling tidal_get_playlist_image by the word 'wide'. It is clear, though the differentiation from tidal_get_playlist_image is only implied by one adjective rather than made explicit.

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?

There is no guidance on when to choose this tool over tidal_get_playlist_image, tidal_get_playlist, or the many other image tools in the sibling list. An agent must infer that 'wide' means a non-square aspect ratio, and no prerequisites or exclusions are stated.

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